The Rack + Mod_Rails solution is what I've done in the past, for a web service polling system(1,000's of clients at varying intervals(3-30 seconds) depending on the client's mode).
The speed gain I got from switching this service from part of a Rails app to a standalone Ruby app with a Rack adapter + mod_rack saved so much memory and processor power and really sped things up. Codey On Fri, Feb 6, 2009 at 11:44 AM, ara.t.howard <[email protected]>wrote: > > On Feb 6, 2009, at 11:09 AM, Bothari wrote: > > Group, >> >> At my company I'm looking for opportunities to use Ruby where it makes >> sense. We need a web service that accepts a post of ~200 bytes of >> data from 500 clients ~5 times per second, persists the body of the >> message to a Berkly database and returns a 200. Right now the service >> is fronted by Active MQ, but it falls behind during the peak times and >> we're getting rid of it. The first option is Apache and Tomcat and >> write a simple servlet, but what's a good ruby approach for something >> like this? >> >> Joe >> > > without question simply write in rack and put it on mod_rails/mod_rack. > > extremely fast, robust, and zero maintenance. > > a @ http://codeforpeople.com/ > -- > we can deny everything, except that we have the possibility of being > better. simply reflect on that. > h.h. the 14th dalai lama > > > > > _______________________________________________ > Bdrg-members mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/bdrg-members >
_______________________________________________ Bdrg-members mailing list [email protected] http://rubyforge.org/mailman/listinfo/bdrg-members
