On Mon, Sep 15, 2014 at 3:02 PM, Rodrigo Boavida <[email protected]> wrote:
> Tnks for the reply Patrik. > > Yes we have that option on the table as well, but would each node in the > cluster still participate in the gossip control of all the other nodes, or > would it be confined to nodes within the same role? > They would all be part the same gossip. > > Let me expand a bit on what we have. Both backend and front end (web) are > very much decoupled in terms of purpose. The FrontEnd doesn't always need > the backend layer, could even be offline as the front end has it's own data > access nodes. Depends on what is the user requesting. Backend is also for > other processing functions requested by other entities through an API. They > could also live in different geographies. Bottom line is they don't depend > on each other to exist. > > I guess the only reason I still struggle on accepting having everything > inside the same cluster is because of the "community" concept of the > cluster, where there's common agreement on classifying each node state and > gossiping it around. Wouldn't the backend worker nodes influence judgement > on availability of frontend nodes to other frontend nodes? > > And in terms of seed nodes, I imagine we would need to have four seed > nodes, two for each layer (be and fe) to make sure nodes on both layers > start successfully. > Thanks for clarifying. You have presented several good reason for why they should be separated. The ClusterClient doesn't support publish-subscribe where the subscriber is on the client side. It is designed for the opposite direction. It has been discussed a few times but I'm not sure we came to a working solution. See here: https://groups.google.com/d/msg/akka-user/5sWghsQF9oc/DeQxl6VQfuEJ Looks like a created a small sample: https://gist.github.com/patriknw/6271877 That is extremely untested and only intended as inspiration. Please read that thread and see if it makes any sense for you. I'm happy to try to answer further questions. Cheers, Patrik > > Looking forward on your comments. > > Tnks, > Rod > > > > On Monday, September 15, 2014 11:08:36 AM UTC+1, Patrik Nordwall wrote: >> >> >> >> On Fri, Sep 12, 2014 at 6:26 PM, Rodrigo Boavida <[email protected]> >> wrote: >> >>> Hi Konrad, >>> >>> We have the same requirement. The reason why we need this approach is >>> because we need two types of cluster: Web and Processing cluster. Both have >>> different lifecycles and concerns, but the Web cluster needs to subscribe >>> to data sources processed by the backend cluster. The publisher/subscriber >>> would be ideal as I would only need to connect through the contact points >>> of a cluster client and subscribe to a given topic without being concerned >>> how is the backend implemented in terms of actors and paths. >>> >>> Does this make sense or would you have any other suggestion? >>> >> >> Have you considered using cluster node roles >> <http://doc.akka.io/docs/akka/2.3.6/scala/cluster-usage.html#Node_Roles> >> instead of separate clusters? >> >> Regards, >> Patrik >> >> >>> >>> Many thanks in advance, >>> Rod >>> >>> >>> On Thursday, August 7, 2014 7:48:55 AM UTC+1, 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]> 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/c >>>>> urrent/additional/faq.html >>>>> >>>>>>>>>> Search the archives: https://groups.google.com/grou >>>>> p/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. >>>>> >>>> >>>> >>>> >>>> -- >>>> 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. >>> >> >> >> >> -- >> >> Patrik Nordwall >> Typesafe <http://typesafe.com/> - Reactive apps on the JVM >> Twitter: @patriknw >> >> -- > >>>>>>>>>> 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. > -- Patrik Nordwall Typesafe <http://typesafe.com/> - Reactive apps on the JVM Twitter: @patriknw -- >>>>>>>>>> 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.
