Microsoft Orleans
Shares rank 10 of 11 concurrency libraries by recommenders
A mature .NET framework for distributed actors, praised for its ecosystem and distributed dictionary types. Critics warn its automatic state restoration can cause crashes.
A mature .NET framework for distributed actors, praised for its ecosystem and distributed dictionary types. Critics warn its automatic state restoration can cause crashes.
7 people gave an opinion
- recommend it
- 5
- criticize it
- 2
- approval share
- 71%
Recommended in 4 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: not recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- 2.5 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 4 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Mature project with strong ecosystem
“great ecosystem (orleans, ef core, aspire, asp.net core, blazor, signalr, etc)”
Comment from 8 Jan 2026 in “C# is programming language of the year 2025” “The project has matured nicely over the years”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” Distributed dictionary types for architecture
“The optimal architecture is something like what Service Fabric or Orleans can do with their distributed dictionary types”
Comment from 5 Jun 2026 in “Redis 8.8: New array data structure, rate limiter, performance improvements”
What people warn about
Each mark is one comment
Auto state restoration can cause crashes
“I think their failure handling with auto state restoration is a mistake, recreating an actor with bad state is a recipe for crashes.”
Comment from 12 Oct 2026 in “Choreographic Programming in Rust” Adds complexity to setup
“It just adds complexity to this setup.”
Comment from 18 Dec 2025 in “Systemd v259” Library approach weaker than language-based
“thought the language based approach was nicer than a library based solution like Orleans”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]”
Other concurrency libraries people recommend
The four most recommended other concurrency libraries, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Tokio | 57 | 45 | 56% | 12 | — | — |
| Akka | 12 | 9 | 57% | 7 | — | — |
| ZIO | 11 | 2 | 85% | 9 | — | Approved |
| Trio Python library | 10 | 0 | 100% | 8 | — | Approved |
| Microsoft OrleansThis page | 5 | 2 | 71% | 4 | — | — |
What people said
6 of the 7 comments that mention it, newest first. Each links to the original comment.
“I think their failure handling with auto state restoration is a mistake, recreating an actor with bad state is a recipe for crashes.”
“The optimal architecture is something like what Service Fabric or Orleans can do with their distributed dictionary types”
“thought the language based approach was nicer than a library based solution like Orleans”
“The project has matured nicely over the years”
“great ecosystem (orleans, ef core, aspire, asp.net core, blazor, signalr, etc)”
“It just adds complexity to this setup.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.