Well, A pretty old version is running the NH Prof backend. The idea there was that I wanted the website on _all the time_, and that I really don't want to lose transactions ever. The website doesn't hit any sort of database, it is all generated from local templates, so it is fairly fast. Anything that can go wrong doesn't affect the user experience, and I can replay transactions after the fact. It also means that I can update things in place (well, at least the backend) without disturbance of service.
In one of my clients, we are using this in order to have fast response times, and to handle spikes in traffic. They have the interesting problem that they can have 100 users/sec one minute and 10,000 users/sec the next. Using queues will deal with that problem quite nicely. It also means, again, that we get better error recovery and support options. On Fri, Apr 3, 2009 at 5:27 AM, webpaul <[email protected]> wrote: > > Can you guys give some examples of what you are using RSB for, i.e. > the business need? Or are you just experimenting to see how it works? > > On Apr 2, 5:41 pm, Ayende Rahien <[email protected]> wrote: > > No way I am going to beat anyone, I am taking a flight in a few hours, > going > > to be busy recovering for a few days after that. > > > > > > > > On Thu, Apr 2, 2009 at 6:32 PM, Corey Kaylor <[email protected]> wrote: > > > In a good way. Changes look great. I'll digest and try to put a simple > > > visualizer together over the weekend (wife permitting) if you don't > beat me > > > to it.- Hide quoted text - > > > > - Show quoted text - > - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
