W dniu środa, 15 lutego 2017 17:12:04 UTC+1 użytkownik [email protected] napisał: > > Hi Tal, > > thank you for you tip. > > The answer to your question is: all the examples I've seen so far use one > cluster only. You are right, the task itself does not even require the > manager to be in any cluster if there is exactly one manager. So your > answer is very reasonable. I'll soon check it out. >
Cluster is a heavy-weight resource. It brings on certain administrative challenges, especially when running on a public cloud. Running two clusters when in fact you could run one with two node flavors (roles) is an overkill. > > However, the question that arises is: Is it necessary in Akka that all > nodes of a cluster have the same code base? > No, they don't have to. You just need to make sure that all messages can be de-serialized on the recipient node. There's nothing preventing you from splitting your project into multiple modules and packaging a separate binary artifact for each of the node roles that you require. Having a single artifact is just a simplification. Please note that even if unnecessary code is 1MB of compiled classes (which would require a lot of source code), your final artifact will typically weigh dozens MBs for a .tar.gz to hundreds of MBs for a Docker image. So why bother, actually? Cheers, Rafał -- >>>>>>>>>> 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 https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
