I'm the author of the blog post from Conspire you referenced. In our
case, losing the supervisor isn't a problem because all work is generated
from a SQL database. If the supervisor crashes, we can just start over.
Our worker nodes subscribe to cluster event notifications and will
I wouldn't be surprised if there were also some good options using Akka
alone. On top of my large queue concerns with Rabbit I didn't particularly
feel like adding another component into the mix if I didn't need to. I
wouldn't be shocked if you could do something pretty cleanly with just
This is a copy of a post I put up on
Stackoverflowhttp://stackoverflow.com/questions/23403335/akka-pulling-pattern-vs-durable-mailboxes
.
I've been working on a project of mine using Akka to create a real-time
processing system which takes in the Twitter stream (for now) and uses
actors to
In the new Router documentation for version 2.3.2
(http://doc.akka.io/docs/akka/2.3.2/java/routing.html), I noticed that in
their very first example, they use a new Router class. From the example, it
seems like they use the Router as a group-router since they first create
Worker actors as
I was considering almost the same thing, but talked myself out of it after
reading this: (
http://www.rabbitmq.com/blog/2012/04/25/rabbitmq-performance-measurements-part-2/see
section Large Queues). RabbitMQ queues messages in memory, regardless
of whether they are durable. The
