mirror of https://gitee.com/pnoker/iot-dc3.git synced 2026-10-31 10:11:49 +08:00

Files

T

History

pnoker 372d75b0c9 refactor(core): rename find/query/fetch methods to get per crud law

sweep every module to satisfy the new method-name rule, renaming
about 40 methods together with their interface, implementation, test
and cli call sites: store find() lookups become get(), analytics
queryLatest/queryHistory become getLatest/getHistory, sql helper
query() becomes spec()/sql(), jwks fetch() becomes load(), and the
cursor record component queryDigest becomes requestDigest

no behavior changes; full unit suite (5278 tests) and both quality
gates stay green

2026-09-18 09:53:51 +08:00

dc3-tsdb-core

refactor(core): rename find/query/fetch methods to get per crud law

2026-09-18 09:53:51 +08:00

pom.xml

refactor(storage)!: unify platform persistence on reactive postgresql

2026-09-01 22:03:16 +08:00

README.md

refactor(storage)!: unify platform persistence on reactive postgresql

2026-09-01 22:03:16 +08:00

README.md

DC3 TSDB

dc3-tsdb contains the store-neutral reactive time-series contract used by the Data Center. Relational point history is implemented by dc3-common-data's native R2DBC store; no synchronous JDBC or pseudo-reactive adapter is shipped.

Modules

Module	Role
dc3-tsdb-core	store-neutral reactive `TsdbStore` port, `TsdbModel` sample model and capability set

Selection

The active relational store is the R2DBC connection configured by the Data Center. There is no runtime adapter selection and no JDBC fallback.

Build and verify

mvn -s .mvn/settings.xml -q -f dc3-tsdb/pom.xml -DskipTests compile
mvn -s .mvn/settings.xml -f dc3-tsdb/pom.xml test

The reactive boundary and migration gates are documented in docs/design/relational-r2dbc.md.