Anyone know of any articles that explain the architecture differences of moving from an app server to Apache + fast_cgi? Basically I want to know things like: 1. Are global variables possible? Since each process in fast_cgi is its own environment I guess its not possible, which is why you cannot have a connection pool in this type of environment. On that same note, is 2nd level cache possible? Would there be a 2nd level cache for each process? 2nd level cache for O/R - To be able load a record once for the entire life of the application or expire it after a period of time. 2. Is it possible to have a load balanced and fault tolerant environment with DRB or Memory Store session management? Meaning any time a session changes the session is replicated to another server. So you can have a ring of servers that back each other up to have a fault tolerant environment. I have seen articles/blogs about language differences between Java and Ruby which helped a lot. Now I''m curious about App Servers and Apache + fast_cgi. Thanks a lot for your help.
* Joe Toth [2005-09-15 13:29]:> Anyone know of any articles that explain the architecture differences > of moving from an app server to Apache + fast_cgi?You''re basically looking at moving from a threaded architecture to a process-oriented one. They just happen to be java and ruby in your question. This should get you started, and it''s even re: Rails http://blogs.codehaus.org/people/tirsen/archives/001041_ruby_on_rails_and_fastcgi_scaling_using_processes_instead_of_threads.html or better: http://rubyurl.com/I0v (I could hear the gears grinding on rubyurl, hope it''s still healthy when you try this) -- ________________________________ toddgrimason*todd[ at ]slack.net
using memcache you can do the number things your questioning. memcached will let you have "GLOBAL" variables per-say. it will let you cache as much of the db you want as wide/narrow (per-process) as you want. it will allow you to make sessions GLOBALLY accessible and without the huge hit a database backed session manager would. http://www.danga.com/memcached/ On 9/15/05, Todd Grimason <todd-cwT7Wi5Y1r1eoWH0uzbU5w@public.gmane.org> wrote:> * Joe Toth [2005-09-15 13:29]: > > Anyone know of any articles that explain the architecture differences > > of moving from an app server to Apache + fast_cgi? > > You''re basically looking at moving from a threaded architecture to a > process-oriented one. They just happen to be java and ruby in your > question. This should get you started, and it''s even re: Rails > > http://blogs.codehaus.org/people/tirsen/archives/001041_ruby_on_rails_and_fastcgi_scaling_using_processes_instead_of_threads.html > > or better: > http://rubyurl.com/I0v > > (I could hear the gears grinding on rubyurl, hope it''s still healthy > when you try this) > > -- > > ________________________________ > toddgrimason*todd[ at ]slack.net > > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Zachery Hostens <zacheryph-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>