Akka's Actors are different from EJB's remote session beans. There is some usage overlap, as both Akka and EJB provide a way to do remote procedure calls, howev

Akka's Actors are different from EJB's remote session beans. There is some usage overlap, as both Akka and EJB provide a way to do remote procedure calls, however there are differences in the approaches used. For me the Actor model [1] is saner. Also, Actors aren't only about RPC. All my actors are in the same process, being a capable multi-threading model. And Akka isn't only about Actors anymore. Scala's Future/Promise interfaces were nurtured in Akka and Akka 2.2.0 includes a cool foundation for asynchronous I/O [2], being an alternative to Netty and Mina. It's an awesome library. [1] https://en.wikipedia.org/wiki/Actor_model https://en.wikipedia.org/wiki/Actor_model [2] http://doc.akka.io/docs/akka/2.2.0/scala/io-tcp.html http://doc.akka.io/docs/akka/2.2.0/scala/io-tcp.html