I would absolutely recommend nginx for production use.
It does the load balancing pritty well and I had myself asked for advice
on the approach and reverse proxy with paist has given me the best
performance.
Happy hacking.
Krishnakant.
On 09/03/12 00:27, Jonathan Vanasco wrote:
Not talking about Pyramid / WSGI layer itself...
Assuming that these are just "skinning" a platform for customers, I
would keep away from running each application on a separate IP and try
to handle them via virtualhosts. The rationale for this is:
1. It's easier to step& repeat for new clients
2. If you hit bottlenecks, you can scale out all of one component at
the same time
3. In terms of server maintenance, you'll have different types of
exact setups for machines.
You probably are planning for this already, but i'll mention anyways
-- you'll also want to have Varnish and/or Nginx running in front of
your setup. That'll take care of issues from slow-connections and
offload any static serving from whatever WSGI server you choose.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
