Thanks John & Kenneth! I will use thin gem for some time and I will try to do some performance tests. I hope it will be enough. At the moment, it seems the easy way :)
On Wed, Jun 3, 2009 at 8:54 AM, Kenneth Kalmer <[email protected]>wrote: > On Wed, Jun 3, 2009 at 1:30 AM, John Mettraux <[email protected]>wrote: > >> >> On Wed, Jun 3, 2009 at 12:54 AM, Diego Moreno <[email protected]> wrote: >> >> > I am thinking about two posibilities: >> > >> > * Using nginx as a request dispatcher to serve requests torwards a >> mongrel >> > cluster. This is a good deployment for rails applications and it is >> surely >> > useful with concurrent requests. But I don’t know how to make mongrels >> share >> > a single workflow engine instance (ruote instance). >> >> Others, like Kenneth, have taken the ruote-rest way (and later >> ruote-kit) to let the workflow engine sit in a web application behind >> the front web application[s]. >> > > Hi Diego > > We've discussed this issue on the list before at > http://groups.google.com/group/openwferu-users/browse_thread/thread/bbea87de0e7b5bce/3b8d3cb6998b73c3, > but I'll summarize it for you again. > > The problem with running multiple instances of the engine (inside > mongrels/passenger) is that you'll have the schedulers tramping all over > each other, amongst other things. John and myself have discussed some > conceptual enhancements to ruote that would allow for multiple instances to > run together, but those chats were more of a "wow, that would be awesome!" > nature than anything serious. > > We using ruote-rest in production, and a few other members of the group do > too. Rails than polls ruote-rest for workitems, and launches processes, etc, > much the same way it would use a database. Actually, ruote-rest can be > thought of a workitem database :) > > I've extracted some our production code and smacked it on github [1] that > shows how we go about this. The code is first iteration and is going to > evolve into a Ruby gem that will be the client for ruote-kit. > > In close, if your userbase is small and request volumes low, stick to a > single evented server like thin and possible enable threadsafe mode inside > rails (making sure your code is threadsafe). That should give you decent > milage before needing ruote-rest. If however this is not the case, and > you'll need to do a lot of requests, strip the engine out of rails and get > ruote-rest behind it as quickly as possible. > > [1] http://github.com/kennethkalmer/ruote-rest-rails-client > > > -- > Kenneth Kalmer > [email protected] > http://opensourcery.co.za > @kennethkalmer > > > > > --~--~---------~--~----~------------~-------~--~----~ you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
