Celebrity Deathmatch: Akka.NET vs Orleans
summary
Direct comparison of two .NET actor frameworks: Akka.NET uses local object references, offers 10 million msgs/s in the presenter’s laptop benchmark, favors explicit control with props, actor refs, event-sourced persistence and supervision that escalates failures to parents; Orleans forces message serialization, shows ~5,000 msgs/s in that benchmark, provides a client library and injectable grain factory, virtual actors with cluster-wide IDs and simple state objects persisted via providers. Benchmarks favor Akka.NET for raw throughput and memory (≈900 bytes/actor); Orleans trades some performance for safer defaults and easier adoption.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:27Why use actor frameworks
- 9:10Actor model history
- 14:05Akka.NET vs Orleans concepts
- 19:41Coding style differences
- 25:17Actor lifecycle
- 30:38Hierarchy and sharding
- 36:58Exception handling
- 42:33Client interaction
- 46:48Data persistence
- 52:09Cluster setup
- 54:15Performance comparison
- 57:01Final thoughts
- 1:00:12Q&A
related talks
01h 01mCelebrity Deathmatch: Akka.NET vs Orleans
01h 14mAkka.NET: The Future of Distributed Programming in .NET
44mDeath to Latency: Building Reactive, Cloud Native Apps with Akka NET
39mAkka.net: The actor programming model
39mActors can rule your DDD world
50mActors can rule your DDD world
47mNetworks and Types — the Future of Akka
55mCode it like C#, run it like Erlang
