01 · plant or edge
OrdinateDB at the edge
Collectors write locally before forwarding. Current values and local history remain available in the operational environment.
Architecture
One model at the core. Deployments shaped by operational need.
OrdinateDB connects collection, storage, context, calculations, events, visualisation and access without turning them into separate product boundaries.
Unified core
SPEC 01The model is the joining point.
A stream keeps one identity as it moves from collector to storage, asset, calculation, display and API. Context and governance do not have to be reconstructed at every boundary.
OrdinateDB · one model
Collection
OPC UA · MQTT · gRPC · batch
Storage
live · warm · long-term
Context
assets · streams · relationships
Logic
calculations · events · episodes
Use
visualisation · reports · applications
Control
permissions · versions · lineage
Distributed deployment
SPEC 02 §6 · SPEC 03 §8Put each instance where its work belongs.
Architecture follows network and operational boundaries rather than licence editions. This is forwarding and recovery by explicit mechanism; it is not a claim of synchronous clustered operation.
02 · network boundary
Interrupted uplink
A disconnection becomes buffered backlog and an explicit gap state, not an excuse to invent continuity.
03 · business or managed
Another OrdinateDB instance
History is forwarded to the environment where wider users and applications can access it without loading the control system.
local WALstore-and-forwardContinuous chunk shipping
Resilience by mechanism
Show the recovery path, not an availability slogan.
Buffer before transmit
The collector records to local disk before attempting the network path.
SPEC 02 §6Acknowledge after durable write
The server acknowledges a batch after its write-ahead record, then the collector can trim.
SPEC 02 §5 · §10Make gaps structural
Collection outages and buffer limits create gap markers with causes.
SPEC 02 §9.3Keep chunks immutable
Checksums, copy-forward compaction and rebuildable indexes make recovery inspectable.
SPEC 03 §4 · §8Practise restore
Backup and restore are documented operations whose results can be retained as evidence.
SPEC 03 §8–9Public interfaces
SPEC 13 §1The product uses the same API you do.
OrdinateDB visualisation and administration are ordinary clients of the versioned public API. REST, streaming, gRPC ingestion and the CLI share identity, permissions and audit behaviour.
REST / JSONmodel, queries, configuration and jobs
WebSocket / SSElive values, quality, events and progress
gRPCdocumented custom collector ingestion
ordctlthe same operations for scripts and CI
Read the source-derived API reference →