Actors can rule your DDD world
summary
Shows using Akka.NET on .NET 6 to host DDD aggregates inside persistent actors, wiring CQRS command routers to per-aggregate actors and projectors for read models. Claims event-sourcing is built in, measures overhead at about 400 bytes per actor, and cites a vendor claim of 50 million messages/sec while reporting over 4+ million/sec on a five-year-old laptop. Demonstrates snapshotting (example: save every 100 events), router pools to scale, and a beer-shipping example that composes and replays domain events.
AI-written summary · about
chapters (21)
- 0:00Start
- 4:24What is Akka.NET?
- 8:03The simplest actor
- 10:00The ActorSystem
- 12:31Actor hierarchy
- 13:13Creating Children
- 16:35Supervision
- 19:36Disclaimer
- 20:18Aggregates
- 20:37Base behavior
- 21:32Implementation (State)
- 22:25Implementation (Commands)
- 22:57Implementation (Events)
- 23:31Test base class (1)
- 24:12Clean Test
- 25:08Base Actor (1)
- 28:02Implementations
- 28:42Aggregate manager.
- 29:02Command Router
- 29:30Projectors
- 32:51Things we didn't talk about
related talks
50mActors 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
