Hi Kuangwei,
Hi Wil,
there are solutions based on redis like Resque from the github guys.
Personally I like beanstalkd, because its simple and fast. Resque offers
a lot more features (especially more management), but it comes with more
overhead.
Redundancy is good, but if your using beanstalkd as async queue you may
just tolerate the failure of one node and run the jobs later on after
restoring the host. You can easily use multiple beanstalk server at once
and do some kind of loadbalancing between them. You will just loose some
jobs in case of a failure, which would run later after the host was
restored. Just my thoughts ;-).
Jan
--
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.
