inline. On Wed, Jan 28, 2009 at 2:05 PM, Matt Burton <[email protected]> wrote:
> > I have a scenario where I want to have multiple subscribers to a > message such that when the message is published each picks it up and > processes it independently. In terms of config I don't want to have > the publisher know about each worker node, so I was able to get the > load balancer concept running and it works just as I had hoped. > That should work out of the box. Although I should note that what you are talking about here is pub/sub, not load balancing. > > Question - the scenario I'm proving out here is one where I'm > provisioning software to machines, so that I receive a request to > provision a new tenant and then I publish a message to create a new > web site for that tenant on N machines. I want to be able to throw a > new box into the mix and have it participate in the process > automatically. Try it :-) It will work > It would be nice to know whether or not the > provisioning of the web site was successful on each machine and base > the completion of the saga on whether or not all boxes chimed in > saying they were successful. In order to do that, however, I'd need to > know how many servers were participating, something which looks like > it would require some tinkering around with the actual subscription > queues themselves to figure out. > You can do report success/failure instead. It breaks the notion of service independence to know about subscribers. At that point, you are making decisions based on things that you do not control. What you might want to do is to have an explicit registration step, instead of publishing. > What would you advise in this scenario? Fire and forget for > provisioning the sites - depend on an external solution to monitor > errors? Or do I have the workers send back a thumbs up saying that > they did their job and when all report back call it good? If so, what > are my options for determining the number of subscribers in the load > balanced scenario? > You can get ISubscriptionStorage and ask it for that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" 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/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
