Akka.net
Canonical actor model implementation for .NET with local + distributed actors in C# and F#. (by akkadotnet)
.NET port of LMAX Disruptor
Port of LMAX Disruptor to .NET (by disruptor-net)
Our great sponsors
| Akka.net | .NET port of LMAX Disruptor | |
|---|---|---|
| 20 | 2 | |
| 4,607 | 1,159 | |
| 0.7% | 1.1% | |
| 9.3 | 7.2 | |
| 3 days ago | about 2 months ago | |
| C# | C# | |
| GNU General Public License v3.0 or later | 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.
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.net
Posts with mentions or reviews of Akka.net.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-20.
-
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
.NET port of LMAX Disruptor
Posts with mentions or reviews of .NET port of LMAX Disruptor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-21.
-
Is there a library with a fixed-sized collection, where newly added data is inserted at the start, but if the collection's capacity has reached the size, older data is discarded (but it doesn't move any of the elements around), and that you can also index to?
You could consider looking at https://github.com/disruptor-net/Disruptor-net.
-
Awesome .NET Performance
I would look at adding LMAX Disruptor to this list. It can run circles around stuff scattered across TPL usages. Doesnt fit every use case, but its really incredible when it does fit. I was able to build a toy project that handles millions of user events per second on a single thread using this.
Getting your application aligned with the NUMA model makes way more difference in performance than anything else.
What are some alternatives?
When comparing Akka.net and .NET port of LMAX Disruptor you can also consider the following projects:
protoactor-dotnet - Proto Actor - Ultra fast distributed actors for Go, C# and Java/Kotlin
Orleankka - Functional API for Microsoft Orleans http://orleanscontrib.github.io/Orleankka
Orleans - Cloud Native application framework for .NET
.NEXT Raft
MBrace - MBrace Core Libraries & Runtime Foundations
Zebus - A lightweight Peer to Peer Service Bus
IdGen - Twitter Snowflake-alike ID generator for .Net
Websocket-Sharp - A C# implementation of the WebSocket protocol client and server
FsShelter - Author Apache Storm topologies with F# using statically-typed streams
Akka.net vs protoactor-dotnet
Akka.net vs Orleankka
Akka.net vs Orleans
Akka.net vs .NEXT Raft
Akka.net vs MBrace
Akka.net vs Zebus
Akka.net vs IdGen
Akka.net vs Websocket-Sharp
.NET port of LMAX Disruptor vs Zebus
.NET port of LMAX Disruptor vs protoactor-dotnet
.NET port of LMAX Disruptor vs Orleankka
.NET port of LMAX Disruptor vs FsShelter