Hello Todd, it seems that routers and particularly cluster aware routers <http://doc.akka.io/docs/akka/2.3.9/scala/cluster-usage.html#Cluster_Aware_Routers> fit the bill here. Did you have a chance to look at them?
On Sun, Mar 15, 2015 at 11:37 AM, Todd Nine <[email protected]> wrote: > Hey guys, > We're currently using RxJava, and we would like to attempt to integrate > Akka as a our distributed work system in the Usergrid project. > > http://usergrid.incubator.apache.org/ > > > I've gone through a lot of the typesafe activator examples, and they're > very helpful. However, there's 1 use case I could use some guidance on. I > need the ability for a distributed work system, similar to this example. > > > http://typesafe.com/activator/template/akka-distributed-workers > > > Our flow is the following. > > > 1. User makes an HTTP request, PUT or POST > 2. We store the entity they've uploaded into Cassandra > 3. We signal a asynchronous worker to start indexing this entity. > This will need to be a durable mailbox so if the processing node dies > before completion, it will be replayed on another node. We'll probably use > the Cassandra persistence here for recovery and durability. > 4. The worker begins performing the indexing of the entity to > ElasticSearch asynchronously. > > > The example from the typesafe activator uses a "master" to perform routing > to it's workers. I have a few questions. > > > > 1. Is it possible to perform the same workflow, but with round robin > message distribution and no routing through the master? I'd prefer the > message is delivered directly to the worker, if possible. > 2. For the actor system, how would I insatiate N workers per node? > Must I always have a supervisor actor that then starts workers? I assume > so given the actor model, but wanted to ask to be sure. > 3. Using the clustering and Gossip, is there some discovery mechanism > I can use so that all workers across all nodes appear as one large pool of > workers, and the producer does not need any knowledge of the other node's > IPs as remote workers? > > Sorry if these questions are obvious. I'm learning, and most of the > examples seem to reference remote actors by IP. If possible, I would > prefer to abstract this routing away from our system, and instead have > workers appear as one large pool, regardless of location. I'm thinking > we'll be starring with Akka 2.3.9 and Java 8. > > Thanks in advance, > Todd > > -- > >>>>>>>>>> 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. > -- Martynas Mickevičius Typesafe <http://typesafe.com/> – Reactive <http://www.reactivemanifesto.org/> Apps on the JVM -- >>>>>>>>>> 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.
