Supposing I have a central server with a queue that handling logging of events, and a number of satellite servers that generate events which need logging, then an obvious way of handling those events will be for the satellite servers to push the events to the central queue.
However, if I want the whole thing to be resilient to network failure, each server would need its own local queue to write to, if the central queue could not be reached. Events written to local queues would need to be moved to the central queue as soon as the network is back up. Is there a ready made solution that will handle that? It needs to check queue A on server A, and if anything is found, moved it (reliably and robustly) to queue B on server B - that would be its sole purpose. Whether it would be a push or pull process (or even a pull-push from server C) is not, I suspect, not important. Thanks, -- Jason -- 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.
