Akka
Akka.net
Our great sponsors
Akka | Akka.net | |
---|---|---|
33 | 20 | |
12,905 | 4,593 | |
0.3% | 0.7% | |
9.4 | 9.3 | |
7 days ago | 6 days ago | |
Scala | C# | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
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.
Akka
-
Modern Async Primitives on iOS, Android, and the Web
Kotlin also has a construct for asynchronous collections/streams. Kotlin's version of AsyncSequence is called a Flow. Just as Swift's AsyncSequence builds upon prior experience with RxSwift and Combine, Kotlin's Flow APIs build upon earlier stream/collection APIs in the JVM ecosystem: Java's RxJava, Java8 Streams, Project Reactor, and Scala's Akka.
-
What are the current hot topics in type theory and static analysis?
First-class distributed and multicore computing. Swift has first-class “actors” and “distributed” methods. Unison, Erlang, and Elixir are built with distributed being one of the #1 concerns. Though first-class is not super common and I don't really expect it to be because usually libraries are enough (e.g. Scala has Akka and is used WIDELY for distributed); whereas something like linear types and typed effects, you can't emulate in a library.
-
Anything close beam/otp for other languages?
Akka is a library that implements the actor model for JVM languages. Mainly in Scala, but you can use it in Java too, and maybe others. It doesn't feel as ergonomic as Elixir, but if Elixir is too "out there" for the decision makers in your case, this might be a friendlier alternative.
- 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/
Akka.net
-
MassTransit with MSMQ vs RabbitMQ
If it's the former you may want to take a look at something like the actor model akka.net with persistent actors (https://getakka.net/articles/persistence/architecture.html). No need of an external message broker or mass transit (which is a wrapper over different message brokers). You could use sqllite for persisting the actors state to recover in case of a restart.
-
Learning resource for seniors
Is akka a good alternative?
- Carl Hewitt has died [pdf]
-
Using functional extensions in production C# code?
However, I've found that sometimes, they are a little -too- functional. I'm a bit more preferential to Akka.Net's implementation of Option and Try, if only because they have good 'escape hatches' where you interrogate them in a more procedural manner.
-
Microsoft RulesEngine. Feedback from those that have used it in enterprise environments
This project is also what ultimately led to the creation of Akka.NET - I wrote an overview on how our application was built here: https://aaronstannard.com/markedup-akkadotnet/
-
What does the .NET ecosystem offer in terms of distributed data processing frameworks?
From the title I immediately thought AKKA.NET or Orleans
-
Actor Frameworks
https://github.com/akkadotnet/akka.net/pull/5527 - thanks for letting us now
We're in the process of updating and re-organizing our documentation as we speak, per this issue one of our employees is working on https://github.com/akkadotnet/akka.net/issues/5483 - as our documentation is indeed outdated in a number of areas, hence why I spent most of last week of December painstakingly defining our hygiene for contributing documentation going forward: https://getakka.net/community/contributing/documentation-guidelines.html
-
Why do some people hype MailboxProcessors?
Akka .NET - much more complete and enterprise-level actor model implementation.
- On the Future of Akka and Lightbend
What are some alternatives?
Vert.x - Vert.x is a tool-kit for building reactive applications on the JVM
protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
Apache ZooKeeper - Apache ZooKeeper
Hazelcast - Hazelcast is a unified real-time data platform combining stream processing with a fast data store, allowing customers to act instantly on data-in-motion for real-time insights.
Orleankka - Functional API for Microsoft Orleans http://orleanscontrib.github.io/Orleankka
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.
Orleans - Cloud Native application framework for .NET
JGroups - The JGroups project
.NET port of LMAX Disruptor - Port of LMAX Disruptor to .NET
Lagom - Reactive Microservices for the JVM
Atomix - A Kubernetes toolkit for building distributed applications using cloud native principles
Finagle - A fault tolerant, protocol-agnostic RPC system