Telecom
Network telemetry at line rate — flow records, cell KPIs, and live element state from one engine.
The problem
Why this is hard today
Network telemetry is relentless: flow records, interface counters, and radio KPIs arrive continuously from thousands of elements, and the interesting questions are about right now — which cells are degraded, which links are saturating, which elements went quiet.
The common stack splits this across a stream processor for windowed KPIs, a cache for element state, and a warehouse for history — three systems, three schemas, and reconciliation glue that itself becomes an outage source.
The fit is one engine that ingests at line rate with backpressure, maintains per-element current state as O(1) reads, and computes windowed KPIs continuously — with the full history durable underneath.
Where NYXDB fits
Use-case journeys
Flow & counter ingest
Absorb bursty flow-record and counter streams durably, with backpressure instead of data loss.
IoT & telemetryNOC observability
Continuous transforms turn raw telemetry into live per-cell and per-link KPI tables.
Observability & logsReal-time dashboards
Dashboards read pre-aggregated keyed tables and subscribe to live updates.
Real-time dashboardsArchitecture
How NYXDB fits network telemetry
Flow records and KPIs append at line rate under the memory governor; keyed tables hold the latest state per element; continuous transforms maintain windowed KPI tables that dashboards read as ordinary tables.
- 01
Line-rate ingest
Shard-owned, lock-free write paths, WAL-backed, governed under pressure.
- 02
Element state
Keyed tables keep the latest per (element, metric) — O(1) reads.
- 03
Windowed KPIs
tumble/hop windows maintained continuously by transforms (ADR-080).
- 04
Live streams
STREAM SELECT pushes KPI deltas to NOC dashboards as they commit.
Real SQL
Representative queries
SELECT cell_id, sinr_db, prb_utilizationFROM cell_stateWHERE sinr_db < 5 OR prb_utilization > 0.9;Every statement follows the engine’s own test SQL shapes. See the SQL reference for full syntax.
Capabilities
What you get
Line-rate ingest
Lock-free shard-owned write paths.
O(1) element state
Latest reading per element, instantly.
Windowed KPIs
tumble/hop maintained continuously.
Live push
STREAM SELECT to NOC dashboards.
Proof
Measured on the vetted benchmark lane
durable telemetry ingest, single core
1M-row batches, best durable mode
vetted table
View benchmark268nsper-element state count, flat 1k–16k keys
O(1) maintained counter
vetted table
View benchmark~2.56µsevent → subscriber propagation
flat, empty to a 2M-row tail
vetted table
View benchmarkMeasured on AMD EPYC 9554P 64-Core Processor (64t), 1505GB RAM, 6x NVMe — measured on server-class hardware. Release build, median of 5 (re-captured stragglers: median of 3), commit-pinned (7945ae33, 2026-07-09). Ingest figures are engine-side. See the full benchmark suite.
Learn more