/
Ambitwin · source-available, not open source · © 2026 Nicolò Ghignatti
| Word | Meaning | Example |
|---|---|---|
| Tick | Everything one building reports at one moment | One batch of readings |
| Feed | The live stream of one building | Channel for Northfield Library |
| Columns | Which metrics a building’s table shows | Room name, max occupancy, temperature |
| Catalog | The list of every metric the platform knows | temperature, °C, from telemetry |
| Pub/sub | Send to whoever listens now; nobody listening, message gone | Redis channel |
Realises part of the Telemetry Distribution domain, with socket. Rust, MongoDB. Code-level page: Dashboard Service.
Two jobs:
flowchart LR
T["telemetry"] -. "every tick" .-> D["dashboard"]
D -. "one feed per building" .-> S["socket"]
C["client"] -- "columns, catalog" --> D
Tw["digital-twin"] -- "starting columns" --> D
D -- "catalog?" --> T
D -- "catalog?" --> TwDotted: Redis. Thin: a request.
No layers on purpose: there is no domain logic to protect. Two loops share one in-memory map.
flowchart LR
API["HTTP: columns, catalog"] --> MAP["Map in memory: building to columns"]
TUN["Router loop"] --> MAP
API -.-> DB[("MongoDB")]
DB -. "read once at start" .-> MAPflowchart LR
In["Tick on telemetry:raw"] --> Q{"Building in the map?"}
Q -- "yes" --> Out["Same bytes to that building's channel"]
Q -- "no" --> Drop["Dropped"]Example. Northfield Library shows 2 columns, but its sensors send 5 metrics. All 5 reach the browser. The table shows 2, the 3D view colours rooms by any of the 5.
dashboard does not define metrics. It asks each source for its own list and merges them.digital-twin, so a failed call leaves a building dark until someone saves columns.