Actors can rule your DDD world
summary
Builds BeerSender.net using .NET 6 and Akka.NET to implement event-sourced aggregates with CQRS: actors hold aggregates, persistence IDs must be unique, snapshots every ~100 events, and recover replays events. Architecture uses an aggregate manager, a command router (bottleneck mitigated by router pools and consistent hashing), projector actors for read models, and external subscribers. Claims throughput up to 4 million messages/sec on a laptop (50M/s cited for server JVM), and mentions Phobos telemetry (~€4k/year) for production visibility.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:11Speaker background
- 0:44Agenda overview
- 1:17The beer sender problem
- 4:23DDD and CQRS integration
- 6:02Event sourcing approach
- 8:41Why Akka.NET
- 11:30Actor basics
- 12:59Message handling and throughput
- 15:24Actor system orchestration
- 17:51Actor hierarchies
- 21:03Supervision strategies
- 23:54Akka persistence
- 27:14Persisting and snapshots
- 29:23Aggregate implementation
- 33:16Connecting aggregates
- 36:13CQRS architecture
- 39:23Routing and event bus
- 42:39Future considerations and tools
- 45:24Q&A and conclusion
related talks
39mActors can rule your DDD world
55mCode it like C#, run it like Erlang
01h 14mAkka.NET: The Future of Distributed Programming in .NET
52mDrinking a River of IoT Data with Akka.NET
01h 01mCelebrity Deathmatch: Akka.NET vs Orleans
51mBuilding concurrent systems using Akka.NET
48mProcess IoT information using Akka.NET
01h 01mCelebrity Deathmatch: Akka.NET vs Orleans
