dotNext VS Akka.net

Your example runs as I'd expect. I'm using DotNext's TypeMap and am not understanding why underlying arrays (entries) are indexed differently for two instances of the same type am seeing what I expected. I obviously idioted.

"DotNEXT" is a repo that enhances the code from .NET core, and has examples of using new API's that you can't even find tutorials for on the internet/examples from in public code.

For instance, there's been a class since .NET 6, "RandomAccess", for high-performance random-access file I/O (potentially async), and I couldn't find a single damn use of it on the internet.

But then this repo had a whole utility class for it, and it's chock full of similar things:

https://github.com/dotnet/dotNext/blob/d4111528297ff3b6567b9...

Similarly, I would recommend stuff by the .NET core team.

I'm particular biased towards the low-level/interop team. Anything by Tanner Gooding is great, stuff by Michal Strehovský, Aaron Robinson, Elinor Fung.

DotNext

Someone else used the name dotNext since MS didn't

akka.net actors. Actors all the way! https://getakka.net

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.

Spring and Hibernate are the goto libraries in Java land and I suspect that's the primary motivation for your colleague's recommendations. It's quite easy to bulldoze someone less experienced with your ideas so be careful of that. I'd avoid both. They aren't bad libraries at all but they have a 'legacy' feel and it will make your application less future proof. Would a distributed system be viable? If so then I'd recommend Akka, there'a .NET port of it that's well supported and maintained.

Is akka a good alternative?

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.

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/

You may also want to take a look at queues (e.g. RabbitMQ) or even something like Akka.NET or Microsoft Orleans.

From the title I immediately thought AKKA.NET or Orleans