Hi all. I have a question based on the Activator template "akka distributed workers". I have already written a system very similar to this one. The main difference is that I don't have the workers register with the master. The master simply uses a cluster-based router to round-robin out work to anyone who is in the cluster with that worker path. This way, I don't have the complexity of having the workers constantly having to send out a registration message, I simply let the cluster router handle it with any worker actor who is currently up and in the cluster.
But I feel like I might be missing something that this registration model provides, that maybe my views on this are too simplistic and there's a good reason for this model. Can anyone help me in understanding what might be the main deficiencies in my approach, and what I would gain by having a registration mechanism from workers to master? (I am using the Cluster Singleton approach for my Master actor, which works very nicely because I only want on master at a time in the cluster, who pull in work from a DB source, and distributes the work out to available worker actors). Any help and insight is greatly appreciated. I love Akka and the amazing community behind it. --Eric -- >>>>>>>>>> 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.
