Edge device pipeline
Watch a fleet of simulated devices push state changes that land on screen instantly, instead of the page polling for them.
Simulated fleet + a real poll-vs-patch cost comparison: full 900-row re-fetch on a timer versus delta-only patches per event.
- waiting for the next tick…
*the real interval was 120 seconds; this demo compresses it to 6s so the difference is visible without waiting two minutes.
“Built end to end a real-time device-state pipeline: Go services publish events through NATS JetStream, pushed to the UI over WebSockets. It replaced 120-second polling that re-fetched ~900 rows per cycle with instant updates that patch only the changed records in React.”Dell Technologies — Dell Automation Platform · Edge Device Management
How it works
There's no real Go service or NATS cluster behind a public demo page, so the fleet publishing events is simulated in the browser. What isn't simulated is the cost comparison the résumé line is actually about: in poll mode, every tick genuinely re-serializes and re-renders all 900 rows, whether they changed or not. In instant mode, only the handful of rows an event actually touched are serialized and patched.
The 120-second interval is compressed to a few seconds so you don't have to wait two minutes to see a poll land — the ratio between wasted re-fetch and useful patch is real, the clock is just sped up.