4 ms·

So what's the advantage of Akka compared to Remote Stateless Session Beans?

• bad_user 13y ago
  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
• rkuhn314 13y ago
  Actors are inherently stateful, they provide safe encapsulation coupled with patterns for persistence (see https://github.com/eligosource/eventsourced https://github.com/eligosource/eventsourced for example). Other properties are that they have addresses (ActorRef in Akka) which support location transparency, meaning that every actor which has another actor’s ActorRef can send it a message, no matter whether within the same JVM or across the network. Akka’s particular strength is that it enforces actor supervision, making your software design resilient (see http://www.infoq.com/articles/resilient-software-with-akka http://www.infoq.com/articles/resilient-software-with-akka).