Great article! Comparing to multi-threading, I don’t think the industry “forgot” actor model, because an actor is mapped to a thread eventually.
Multi-actors are multi-threading, the key difference in my understanding, is that an actor is a thread that does not share memory, hence there’s no need for synchronization (locks).
Great article! Comparing to multi-threading, I don’t think the industry “forgot” actor model, because an actor is mapped to a thread eventually.
Multi-actors are multi-threading, the key difference in my understanding, is that an actor is a thread that does not share memory, hence there’s no need for synchronization (locks).
What do you think?
"actor is mapped to a thread eventually"
In akka, there are generally many actors to one thread.
discuss.lightbend.com/t/the-relati...
In addition, an actor is not pinned to a specific thread.
With Elixir/Erlang an actor maps, in effect, to a green thread and then many of those map to an OS thread...... so basically the same idea.
So, yes an actor maps to an OS thread but it isn't a one to one relationship.