We've been using Beanstalk as a messaging server and it's been great. What we do is fairly simple.
Every job is in YAML format (could have been JSON or XML). Each one of them has a "reply_tube" field and we put a random tube name in there. After the job is put in beanstalk, the producer starts listening on that reply_tube. The worker simply puts the response in that tube. That's it! Pretty easy. We've been doing this for over 6 months in a high traffic architecture. It's been rock stable. Carl On Jun 17, 10:41 am, Christian-Rolf Grün <[email protected]> wrote: > Hello, > > I am currently evaluating beanstalkd as a message queue solution for > an application. I'd like to know if there are any built-in facilities > for the worker to send back data to the job producer after a job is > done. > > Failing that, can the worker modify the data associated with a job? > Can the producer alter the data of a buried job before kicking it? > > The last resort for sending data back would be the creation of reply > tubes for each job. How expensive is it to create a tube? > > Thanks -- 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.
