Actors are objects that are scheduled on Kernel threads using ForkJoin Pool?
That's how they're implemented yeah - tasks submitted to a pool. But that misses all the things which make the model useful: isolation and location transparency (the most important one!). So you don't care if an actor is on the same node or not, API does not change, and "fits" as it's messaging and not RPC style which hides the fact that things are remote. -- Konrad `ktoso` Malawski Akka <http://akka.io> @ Lightbend <http://lightbend.com> On 31 March 2017 at 12:53:32, kant kodali (kanth...@gmail.com) wrote: -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
