When and How to Use the Actor Model An Introduction to Akka NET Actors

In the era of cheap, commodity cloud computing the actor model is ascendant across all programming languages and runtimes, both for building distributed systems and for creating reactive mobile or desktop applications.

[adrianplavka]

If anyone is interested, this concept is heavily utilized in languages such as Erlang/Elixir - actor model is basically a first-class citizen and you build your programs by using it, making them a perfect language for backend systems.

[yurizappo]

Very nice explanation of the actor model, I'd definitely recommend this video to everyone who is new to the subject.

[SorupJoshi]

One of the simplest explanation I have found.

[victorchisomnwisu]

Looks like I'm relearning Redux. Really great lessons. Thank you for the detailed explanations.

[Mydad-etel]

a great intro to actor model! Many thanks!

[jimhewes]

I have questions about the Actor model but I never know where to ask or discuss them. This is one.
One of the reasons I find the Actor model attractive is that it claims to simplify thinking about concurrency because each actor is single-threaded. But then all the discussions I see about the Actor model has actors arranged in a parent/child tree structure where the children are essentially workers. But if you limit your design to that structure, then normal mutex locking isn't error prone or difficult to think about either.
The difficulty seems to be when you have actors that are arranged as peers. Let's say that actor A sends messages to actor B and to actor C. As a result of that, actor B sends a message to actor C. Now actor C is receiving a message from each of actor A and actor B but they are not necessarily in any order. And if you need for them to be in a particular order I don't know a simple way to deal with that.
In cases like this it seem that the Actor model didn't really simplify concurrency; it just pushed the problem to another part of the architecture.

[timur]

Keeping in mind that akka is in memory, how it provides data durability and concictency or any failovers when things goes bad (application shutdown, network disconnections, etc...)?

[chriscardoz]

Why isn't this using MEF. I've already been through some pain trying to get dotnet standard libraries written for dotnet core web API working with WCF. Now if you change the interface, I won't be able to reuse my dotnet standard libraries with this framework. Please add some consistency

[chriscardoz]

What the hell is up with you guys. I saw a new modular framework yesterday and now this! Can you provide a website where you publish a list of these new frameworks