We're deploying separate wars that contain functional behaviors like: - UI (not play) - Command Handlers - JMS adapter for inbound A - JMS adapter for inbound B
Today... - each one of these is a separate buildable / deployable artifact and each one has it's own ActorSystem. (Applications A, B, C, D) - each artifact runs across multiple VMs for fault tolerance and performance scaling - we're not using node roles yet - some apps are using cluster singletons We're trying to get the best of these behaviors. - a single pub/sub message bus that all ActorSystems can use and minimize a single point of failure - no startup dependencies on the other apps - happy cluster singletons for each application - I can't run behaviors from App A on an App B VM. (separate builds / log files / support focus / testing regression) What I'm thinking is to try: - Use a single ActorSystem name across all applications - On the Application-A nodes, list Application-A nodes first in the seed node list - followed by seed nodes for Application B, C, and D. - On the Application-B nodes, list Application-B nodes first in the seed node list - followed by seed nodes for Application A, C, and D. - Same idea for Application-C and Application-D seed nodes listed first in their own deployment... - Use node roles to get the ClusterSingletons happy for Application A, B, C, D Does this seem like a good plan? :) Thanks! Brian - On Thursday, August 7, 2014 1:48:55 AM UTC-5, Konrad Malawski wrote: > > Hi Brian, > No, PubSub works within a cluster – it needs to know which nodes to send > messages to, right? > However you could have a subscriber that will mediate the messages to the > other cluster via Cluster Client – > http://doc.akka.io/docs/akka/2.3.4/contrib/cluster-client.html > Would that help in your case? > > I'm interested why you need separate clusters – is it that they're "local" > to some resource or something like that? > > > On Thu, Aug 7, 2014 at 5:52 AM, Brian Dunlap <[email protected] > <javascript:>> wrote: > >> Is it possible to connect DistributedPubSub mediators between >> **different** ActorSystems? >> >> In ClusterSystemA we'd like to subscribe to events from the >> ClusterSystemB mediator. >> >> We need **separate** clusters - that's why can't use the same cluster >> name. >> >> >> Thanks! >> Brian - >> >> -- >> >>>>>>>>>> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at http://groups.google.com/group/akka-user. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Cheers, > Konrad 'ktoso' Malawski > hAkker @ Typesafe > > <http://typesafe.com> > -- >>>>>>>>>> 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.
