If you want distributed pub/sub, I would use an actual pub/sub system. Akka can certainly do it, but Kafka or RabbitMQ are built *specifically for that purpose, *especially if you want distributed pub/sub. Of course the publishers and consumers on either end can be Akka-based.
Though there is the distributed pub/sub extension in contrib: http://doc.akka.io/docs/akka/snapshot/contrib/distributed-pub-sub.html On Saturday, January 10, 2015 at 8:34:17 PM UTC-7, manwood wrote: > > I would like to be able to publish messages on an 'message bus' within my > Akka system, rather than force actors to know about the actors that consume > the events they generate (ie. avoid using *context.actorOf*). > > I know there is the event bus construct, but my understanding is this is > limited to operating within a local process. Is there a recommended way of > supporting a properly message-driven Akka architecture that scales across > remote processes? > -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
