On Feb 26, 9:57 am, Raul <[EMAIL PROTECTED]> wrote:

> OK making tons of progress learning here and getting pretty close to 
> deployment and I need a some more guidance.  I've been testing with Nginx as 
> the proxy to my mongrel cluster but I also have a hardware load balancer.  
> Now it seems to me that just using the load balancer to balance among all the 
> mongrels in several clusters across several machines would be simple and work 
> great.  But if I want something other than Mongrel to serve up html, etc. or 
> if I want to add in PHP support then I probably need to stick with something 
> like Nginx or Apache as the proxy load balancer, correct?  

Several issues here:

1) Can you bypass nginx with a hardware load balancer? Answer: yes

2) Is it as efficient? Not quite: nginx is *very* efficient at serving
static images.

3) How does this interact with non-Rails applications: Answer:
depends!
    a) If you can balance on level-7 information (URL for instance)
then it's not a deal breaker
    b) If you can put the different technologies at different IP
addresses, then it's not a deal breaker
    c) If you want and/or need SSL and/or gzip compression, if your
load balancer provides these functions, then it's not a deal breaker.

#3 could go on and on.

> Just to give a bit bigger picture, I have a couple of machines on which I'm 
> going to be running a couple of VMs on with Xen so I'll have at least 4 VMs 
> and lots of mongrels too.  Plus a development server with subversion and 
> Capistrano to manage all the deployment.

Congrats on your technology stack. You're on a great path, IMHO. :-)

--
-- Tom Mornini


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to