Akka
Ranked 2 of 11 concurrency libraries by recommenders
Actor-model toolkit for building concurrent and distributed JVM systems, recommended for its mature defaults and standardized patterns. The most common caveat is that the license changed to a paid model.
Actor-model toolkit for building concurrent and distributed JVM systems, recommended for its mature defaults and standardized patterns. The most common caveat is that the license changed to a paid model.
21 people gave an opinion
- recommend it
- 12
- criticize it
- 9
- approval share
- 57%
Recommended in 7 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: 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
- 12 people recommend itNeeds 10 or more, met.
- 1.3 recommenders for every criticNeeds 2 to 1 or better, not met.
- Recommended in 7 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 defaults and standardized terminology
“without matching the basic system maturity you get from a default Akka installation”
Comment from 5 Feb 2026 in “Claude Code Agent Teams” “Akka and others have standardized names for all this stuff”
Comment from 19 Jan 2026 in “Gas Town Decoded” Useful for distributed and local concurrency
“they provide a lot of benefit in local single process scenarios too”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” “Akka/Pekko on JVM would be able to do some good with it”
Comment from 3 Mar 2026 in “Intel's make-or-break 18A process node debuts for data center with 288-core Xeon” Preferred over alternatives
“I'd rather just reach for Akka.NET or MessagePipe instead”
Comment from 12 Nov 2025 in “.NET 10” “What I want tho would be Rust+Akka for example.”
Comment from 23 Oct 2026 in “LLMs are making formal software verification feasible at a much larger scale”
What people warn about
Each mark is one comment
License changed to paid model
“I started off using Akka but then the license changed”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” “the boneheaded decision to paywall that ecosystem”
Comment from 29 Nov 2025 in “The Origins of Scala (2009)” “Akka's not open source anymore”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” - Comment from 29 Nov 2025 in “The Origins of Scala (2009)”
Pattern spreads and adds complexity
“the only thing that I hated was how the whole pattern spread through the whole code base”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” “it was always an overengineered approach that made the system more complex for no benefit”
Comment from 2 Feb 2026 in “Actors: A Model of Concurrent Computation [pdf]” “Akka allows writing code that doesn’t make it obvious what is an actor”
Comment from 30 Dec 2025 in “Approachable Swift Concurrency” Hype and relevance have faded
“the hype behind Spark, Akka, Play had already weaned off”
Comment from 30 Nov 2025 in “The Origins of Scala (2009)” “Scala was sold through Akka and Spark, solving pretty complex technical challenges that are less relevant nowadays.”
Comment from 28 Jul 2026 in “Show HN: Scala Tutorials – interactive Scala 3 lessons in the browser”
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 | — | — |
| AkkaThis page | 12 | 9 | 57% | 7 | — | — |
| ZIO | 11 | 2 | 85% | 9 | — | Approved |
| Trio Python library | 10 | 0 | 100% | 8 | — | Approved |
| core.async | 9 | 4 | 69% | 6 | — | — |
What people said
21 of the 25 comments that mention it, newest first. Each links to the original comment.
“What I want tho would be Rust+Akka for example.”
“Scala was sold through Akka and Spark, solving pretty complex technical challenges that are less relevant nowadays.”
“Akka.Net on the .NET side would be able to do some good with it”
“Akka/Pekko on JVM would be able to do some good with it”
“without matching the basic system maturity you get from a default Akka installation”
“I started off using Akka but then the license changed”
“Java's ergonomics, even with Akka, lends its self to certain design patterns that don't lend itself to writing code for distributed systems”
“the only thing that I hated was how the whole pattern spread through the whole code base”
“it was always an overengineered approach that made the system more complex for no benefit”
“they provide a lot of benefit in local single process scenarios too”
“Akka's not open source anymore”
“Don't get me started on Akka.”
“Akka and others have standardized names for all this stuff”
“Akka allows writing code that doesn’t make it obvious what is an actor”
“the hype behind Spark, Akka, Play had already weaned off”
“It's an incredible piece of software but as it turns out, not so many people need stateful cluster sharding.”
“the boneheaded decision to paywall that ecosystem”
“the Akka licensing change”
“I'd rather just reach for Akka.NET or MessagePipe instead”
“Scala has a far more fragmented ecosystem with Cats, Scalaz, Zio and Akka.”
“at a cost of two orders of magnitude more RAM and more CPU”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.