Dear group, at the moment I am looking into akka for back-end batch processing. I know akka is a toolkit, but I am a bit confused by all the choices akka is offering me.
The general idea is simple. One actor (producer) polls a message queue on a regular basis and then relays the messages to specific actors (consumers). The messages itself are just plain JSON with a "type" property that denotes the specific actor that can handle the job. The relay is my problem. What is a good approach? * Should the producer look into message switch over type and tell the correct consumer? * Should I use a BroadcastGroup and let the consumer decide if he wants to handle the message? * Should I use the event bus? Some more details: our consumers are heavy on IO and expected to block and might take a while to finish. The consumer itself fall into several logicals groups, so I really like to have supervision trees. If one crashes, just restart it. Not important if the job finishes or not. We are also a Java shop, so unfortunately no Scala (at the moment). I guess there is no best solution, but some pointers from more experienced folks would be highly appreciated. Thanks in advance! -- >>>>>>>>>> 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.
