Apache ZooKeeper VS Akka

Compare Apache ZooKeeper vs Akka and see what are their differences.

Our great sponsors
  • Sonar - Write Clean Java Code. Always.
  • InfluxDB - Build time-series-based applications quickly and at scale.
  • SaaSHub - Software Alternatives and Reviews
Apache ZooKeeper Akka
32 29
11,032 12,594
0.5% 0.2%
7.9 9.7
2 days ago 1 day ago
Java Scala
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

Apache ZooKeeper

Posts with mentions or reviews of Apache ZooKeeper. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-11.

Akka

Posts with mentions or reviews of Akka. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-01-06.
  • Carl Hewitt has died [pdf]
    5 projects | news.ycombinator.com | 6 Jan 2023
  • About Elixir and the microservices architecture
    3 projects | dev.to | 14 Dec 2022
    Note Akka, the Java & friends framework, is working with the actor model and have as main inspiration Erlang to mimic some features of the BEAM on top of the JVM.
  • Akka will no longer be Open Source
    2 projects | dev.to | 10 Sep 2022
    If I hear about Actor model, the first thing that comes to my mind is the popular Open Source library Akka.
    2 projects | dev.to | 10 Sep 2022
    Lightbend, the company owning Akka, recently shared a blog post signed by the CEO announcing a license change from Apache 2.0 to Business Source License 1.1, a proprietary license. You can already find it in this PR, merged a couple days ago.
  • Why We Are Changing the License for Akka
    2 projects | reddit.com/r/scala | 7 Sep 2022
    Akka 2.6 is on the open source Apache license, that is unchanged (its not possible for Lightbend to change an existing license). Its only the new Akka 2.7 which has the BSL license, so as long as you don't upgrade you are fine. See https://github.com/akka/akka/pull/31561.
  • We Are Changing the License for Akka
    6 projects | news.ycombinator.com | 7 Sep 2022
    Here is Akka's dependency specification: https://github.com/akka/akka/blob/main/project/Dependencies....

    How many of these would have to opt for this source available approach before Akka would no longer be sustainable?

    6 projects | news.ycombinator.com | 7 Sep 2022
    I don't think that the Akka change is aimed at cloud providers. Akka is a toolkit for building highly concurrent, distributed, and resilient message-driven applications for Java and Scala [1]. It's not possible for AWS to offer their own "Akka service" the way they offered Redis through ElastiCache. This change affects companies that build software using Akka, many of which may not be software-focused. For example, here's a case study of an oilfield services company that uses Akka:

    https://www.lightbend.com/blog/low-cpu-utilization-fortune-5...

    [1] As found on https://akka.io/

    6 projects | news.ycombinator.com | 7 Sep 2022
    > So Amazon can take free code, sell it as a slickly-packaged service, and not need to share anything.

    Right, because they didn't change it. So what would there be to share anyway? 'Go to https://github.com/akka/akka'?

    > but it does mean that at least every user has access to the code to make their "Akka Service" as good as Amazon's.

    That code is meaningless. In this scenario we already established that Amazon is selling an unmodified copy of Akka as a Service (which, by the way, we will revisit this point later). And we already established, in your own words, that it's not about the code:

    > Their secret sauce is "we have a Borg Cube's worth of datacenters, so we can run the same code as you at a lower price".

    So what would the SSPL require, they publish their deployment scripts to their cloud datacentres? Like I said, that's meaningless.

    > "Akka Service"

    Final point. There's no such thing as an 'Akka Service'. Akka is a bunch of libraries. You link it into your JVM application. You don't run Akka separately, so by definition you can't offer it as a service (even if you're Amazon).

    Hence my suggestion of AGPL, and heck let's be generous, let's add a commercial use exception for businesses with less than $20m revenue, similar to what they're doing now with the BSL. Except with my suggestion the software would stay as strong copyleft, most businesses would be happy with the commercial use exception, and a few would have to pay their fair share.

    [1] https://news.ycombinator.com/item?id=32751373

  • I need to create an API, but I don't know what framework to use. What would you choose, of you were me, and scalability is a quite important factor?
    6 projects | reddit.com/r/Backend | 31 Jul 2022
    However, if you really expect a lot of users (especially concurrent ones) to use your API, you should delve into the world of reactive programming. Use tools like RxJS (JS/TS) or Project Reactor (Java) in such a case, preferably in combination with a broker like Kafka or RabbitMQ. R2DBC is also great for a data store. Then of course if you want to go one step further, there also exists the less popular but very interesting Actor model which Akka easily has ported into Java.
  • What are Project Loom's Virtual Thread main advantages over platform threads
    2 projects | reddit.com/r/java | 4 May 2022
    What you are describing is more or less the actor programming model. (If you’ve heard of Akka, then you’ve heard of the actor model.) Loom is an enabling technology for implementing the actor model on the (vanilla) JVM, and a lot of people are looking forward to that, including me! So that’s a perfectly valid approach.

What are some alternatives?

When comparing Apache ZooKeeper and Akka you can also consider the following projects:

Hazelcast - Open-source distributed computation and storage platform

Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM

kubernetes - Production-Grade Container Scheduling and Management

Zuul - Zuul is a gateway service that provides dynamic routing, monitoring, resiliency, security, and more.

JGroups - The JGroups project

Hystrix - Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable.

etcd - Distributed reliable key-value store for the most critical data of a distributed system

Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles

consul-template - Template rendering, notifier, and supervisor for @HashiCorp Consul and Vault data.

consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.