On Sat, Aug 8, 2009 at 12:21 PM, Tom<[email protected]> wrote: > On Aug 8, 9:14 pm, Tom <[email protected]> wrote: >> I am a queue newbie and are completely lost in the plethora of >> possibilities. My question is, what I will draft here, the best and >> MOST simple way to reach my goal - and especially is beanstalk the way >> to go? Any pointers really appreciated!
Hi Tom, Your situation sounds like a perfect fit for beanstalkd. Simplicity is one thing beanstalkd has over every AMQP program. Several million messages per day throughput is easy. If you want to get started with basics, there is a tutorial in ruby at http://devver.net/blog/2008/10/ruby-beanstalkd-distributed-worker-basics/ . It has lots of example code. > Concrete questions: > 1.) Should I have two queues per protocol (incoming and outgoing). So > I end up having 6 queues if I use twitter, sms and xmpp? If you have a process that only knows how to handle, say, outgoing sms, it should get its own tube (aka queue). How are the incoming jobs created? Can you generate them all in the same format? If so, you could make one incoming tube, and have one type of worker that handles all incoming jobs, and puts appropriate outgoing jobs into all three outgoing tubes. > 2.) At the beginning a distributed queue doesn't seem necesssary (ruby > should be easily able to deal with this internally) - but maybe later > - a distributed queue may be helpful? I have never heard of anyone outgrowing the performance of a single beanstalkd process on a single box. So, probably, the only reason you would want more than one is for high availability of the service -- if a box goes down, you can still submit jobs to the other one. > 3.) Is beanstalk the best protocol and server to reach my goal or > should I go with a RabbitMQ/ActiveMQ or simple with a DBr solution > that simple shares an/a few internal ruby queue(s)? I'd recommend beanstalkd, but maybe I'm biased. :) Seriously, though, this is just what beanstalkd was designed for. A textbook example. kr --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
