If you work in this space, you owe it to yourself to check out the Retlang library. Comprehensible model, blindingly fast, worked since .NET 2 and... utterly unmarketed.
Retlang was a pioneer in this space for .NET, sadly it never took off more than some initial hype.
But compared to Akka.NET, Akka on the JVM is battle proven for many years now, running backends for Wallmart, LinkedIn etc. So it is good ground to stand on.
Also, Akka.NET compared to Retlang, if I recall correctly, Retlang did about 300 k messages per sec locally, while Akka.NET does 34+ million messages per sec on the same laptop.
I agree Akka has way more mindshare than Retlang/Jetlang. DRW seem to be happy to throw it over the wall but not promote their stuff. I'm curious about the perf figures. Mike was reporting 2.3m msg/s in 2007 and it's seen a number of perf improvements since then (as has hardware :)). Admittedly, I'm sure it could be optimised further since it just uses classic locks.
And this is a single datapoint, I know, but it's _ridiculously_ stable in my experience.
Literally, I've been telling people to just use Retlang since 2007. So many people still just fire up the threads and locks...
