On Jul 14, 7:04 am, James Green <[email protected]> wrote: > I have a project for which I need a distribution of jobs service. > Basically on our office LAN we want to make changes to customer > accounts. On our remote servers these changes need to be picked up and > enacted pretty quickly. > > I can see that each of our servers could contact a queue on the LAN > install of beanstalkd however I was wondering if there were any > replication capabilities even if that's implemented as an external > service/script?
We have an architecture like that in a number of places. For example we use beanstalk for some of our logging (yes, that's probably crazy but reusing infrastructure bits is nice) -- for that we run beanstalkd on each "app server" and then there's a service running that empties that queue and pushes it to a central queue (and from there it gets processed by our summarizer, archived etc). In other instances the setup is more like what you described -- a local queue to queue jobs; the service copies the job to where the workers are. I'm pretty sure we kept at least one of the variants of this service free of our internal stuff so Graham could roll it into a utility script distributed with one of his clients ( http://search.cpan.org/~gbarr/Beanstalk-Client/ and http://search.cpan.org/~gbarr/AnyEvent-Beanstalk/ ) -- but I don't think he got around to it yet. - ask -- 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.
