> I guess the biggest difference I see people talking about when talking > messaging and job queues is that with messaging they expect all > workers to receive all messages. With the 'normal' beanstalkd usage as > a job queue, we expect each worker to see a single 'next job' message > while avoiding all the duplicates. The job queue doesn't work as well > for one to many subscribers, which it seems many people use > queue/messaging systems for.
I don't think that's true. In the messaging world there are queues for point-to-point and there are topics (using JMS terms sorry) for publish-subscribe. When people use a messaging implementation such as amqp or jms for work queueing you do it with a Queue that can have many senders and many listeners. The queue guarantees that only one listener gets a message when it gets put on the queue. As far as I now, this is exactly how beanstalk works. The only thing beanstalkd is missing here is the persistence feature available in the messaging providers already on the market. Any time I've tried to talk about beanstalkd with people they never seem to be able to get past the lack of persistence. As soon as they say "if beanstalk goes down all my messages are lost?", the conversation is over. > The fact that beanstalkd is used for queuing FIFO made sense to me, > but with many other projects focusing on the one to many queues (which > really seems like setting up multiple queues, one for every > subscriber), it might be good to try to clarify the wording a bit on > the site. One of the systems I worked on relied on both messaging paradigms. System-A would send a message out on a topic for anyone who cared to hear about it. System-B would receive a copy of that message and put it into a work queue where one of the many instances of System-C would pick it up and work on it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
