/

Ambitwin · source-available, not open source · © 2026 Nicolò Ghignatti

Dashboard

Keywords on this page
WordMeaningExample
TickEverything one building reports at one momentOne batch of readings
FeedThe live stream of one buildingChannel for Northfield Library
ColumnsWhich metrics a building’s table showsRoom name, max occupancy, temperature
CatalogThe list of every metric the platform knowstemperature, °C, from telemetry
Pub/subSend to whoever listens now; nobody listening, message goneRedis channel

Realises part of the Telemetry Distribution domain, with socket. Rust, MongoDB. Code-level page: Dashboard Service.

Two jobs:


Who talks to it

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?" --> Tw

Dotted: Redis. Thin: a request.


Inside

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" .-> MAP

Routing a tick

flowchart 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.


Columns


Catalog


Gaps