Durable ingest
Writes persisted before acknowledgement.
Line and OEE telemetry, quality-gate state and downtime analytics on one engine, with one keyed row per cell that each plant system extends with its own slice.
The problem
A production line emits a continuous stream of machine, sensor and quality-gate events, and the questions that matter are immediate: which cells are down, which lines are below OEE target, which gate just started failing.
The common stack routes telemetry into a historian, current state into a cache and analytics into a warehouse: three systems whose disagreement shows up as a plant dashboard that trails the line it monitors.
You want one engine that stores line telemetry durably, keeps one row per cell that the MES, the quality station and the maintenance system each own a part of, and computes rollups in the same SQL.
Where NYXDB fits
Architecture
Machine and quality events land in one durable table; a transformation folds them into one slice of the cell table; other plant systems write their own slices of the same row; new slices are added live with ADD ATTRIBUTE GROUP.
Every machine and quality event is durable before it is acknowledged.
One keyed row per cell; a fold owns the activity group.
A new plant system gets its own slice of the row while the fold keeps running, with ALTER TABLE … ADD ATTRIBUTE GROUP.
Cell-state changes reach plant dashboards as they commit, with STREAM SELECT.
In practice
The examples use the same two tables on every page. See the SQL reference for full syntax.
SELECT address, token, amount, updated_atFROM balancesWHERE chain_id = 1 AND address = '0x9c2e4f1a';Capabilities
Writes persisted before acknowledgement.
Each plant system owns a slice of the cell row.
Add a slice to the row while transformations keep running, with ADD ATTRIBUTE GROUP.
A container image or a Kubernetes manifest.
Learn more