InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises. Learn more →
Akka Alternatives
Similar projects and alternatives to Akka
-
-
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
-
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.
-
-
Atomix
A Kubernetes toolkit for building distributed applications using cloud native principles
-
-
InfluxDB
Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.
-
-
-
Elixir
Elixir is a dynamic, functional language designed for building scalable and maintainable applications
-
-
-
ponyc
:horse: Pony is an open-source, actor-model, capabilities-secure, high performance programming language
-
Akka.net
Canonical actor model implementation for .NET with local + distributed actors in C# and F#.
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Akka reviews and mentions
- Carl Hewitt has died [pdf]
-
About Elixir and the microservices architecture
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
If I hear about Actor model, the first thing that comes to my mind is the popular Open Source library Akka.
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
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
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?
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/
> 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.
-
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?
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
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.
-
A note from our sponsor - InfluxDB
www.influxdata.com | 31 Jan 2023
Stats
akka/akka is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.