Drinking a River of IoT Data with Akka.NET
summary
Shows an Akka.NET-based IoT backend that ingests meter readings, normalizes timestamps, interpolates gaps and computes consumption; uses Akka.Remote for proxies to route messages and Akka.Persistence (event sourcing + snapshots) for a single hot actor per device with cold offload to DB. Claims up to 50 million messages/sec but reports 2 million messages/sec on an aging laptop. Describes a gap-fill using the previous week’s trend, supervision/restart strategies, and a working cluster workflow for redeploy and recovery.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:23Agenda
- 0:55A bit of history
- 8:00Introduction to Akka.NET
- 19:19The problem domain
- 22:39How Akka.NET fits in
- 26:20Implementation details
- 27:00Normalizing measurements
- 33:47Getting messages to the ActorSystem
- 39:33Persisting data
- 47:00Restart behavior
- 49:23Beyond this talk
- 50:52Conclusion
- 51:17Outro
related talks
59mDrinking a river of IoT data with Akka.NET
48mProcess IoT information using Akka.NET
50mActors can rule your DDD world
01h 14mAkka.NET: The Future of Distributed Programming in .NET
39mActors can rule your DDD world
31mFun with Sensors
20mBuilding realtime efficient queries in an IOT platform
55mCode it like C#, run it like Erlang
