Using an actor model versus a producer-consumer model?
- by hewhocutsdown
I'm doing some early-stage research towards architecting a new software application. Concurrency and multithreading will likely play a significant part, so I've been reading up on the various topics.
The producer-consumer model, at least how it is expressed in Java, has some surface similarities but appears to be deeply dissimilar to the actor model in use with languages such as Erlang and Scala. I'm having trouble finding any good comparative data, or specific reasons to use or avoid the one or the other.
Is the actor model even possible with Java or C#, or do you have do use one of the languages built for the purpose? Is there a third way?