Beanstalkd is a very good job queue, but I still have following feature requests.
Actually, I am seeking for a lightweight persist topic framework before beanstalk for the requirements of [M pub | N pub] features in my applications. Beanstalk doesn't fit my requests well.
If we can add tube2tube replication in the server side, this feature would be one possible replacement to meet my above requirements.
Refer to following explanation:
pub_1 ... pub_n
it's easy to implement it with a plugin if we only implement put replication in tubes.
I'm not sure I understand this request.
Did you mean to have a single "put" command make many
copies of the job? How do you suggest the server decide
which tube names to copy the job into?
This looks pretty stale, so I'm closing it.
It seems like you're asking for something beanstalkd isn't really designed to do, so as you have observed, it might not be a good fit for you.