ZServer/Apache/Zeus and FastCGI
Does any one have any experience running Zeus with Zope and is it worth the $1700 bucks in terms of performance in the "real world"? Also, I noticed the announcement concerning FastCGI support in the latest Zope release. Will this work with Zeus and or Apache? Is it totally necessary to run ZServer or can Apache/Zeus replace it totally? Sorry for all the questions but I am new to Zope and trying to learn as much about it as I can in a short amount of time. Thanks for the help! Aaron Bostick Exodus Communications
ZServer/Apache/Zeus and FastCGI----- Original Message ----- From: Bostick, Aaron
Does any one have any experience running Zeus with Zope and is it worth the $1700 bucks in terms of performance in the "real world"?
As far as I know, demand in the "real world" rarely makes the average static webserver break a sweat. Unless your projected demand is huge, you should be perfectly happy with Zeus, Apache, or Roxen. It's the dynamic content in Zope which is likely to be the bottleneck.
Also, I noticed the announcement concerning FastCGI support in the latest Zope release. Will this work with Zeus and or Apache?
Works with Apache, certainly. I don't know about Zeus.
Is it totally necessary to run ZServer or can Apache/Zeus replace it totally?
ZServer is the communications module of Zope, and is necessary whether you use it to serve web requests directly or through PCGI or FastCGI with another webserver.
What I would like to know is if there are any easy ways to replicate the ZODB information across web servers if I am running a web farm? In other words, I plan to have multiple identical web servers sitting behind a load balancing appliance so that incoming requests can be sent to any of the web servers. Obviously, the web servers must contain the same data for this to be of any use. If I plan to run a web server and the zope engine on each "web server", how can i replicate changes to all my servers to keep them synced.
ZEO is the subsystem of Zope which handles this. It allows you to run each Zope server as a client of a central storage server, automatically replicating writes to each server as they occur. Alternatively, if all writes are directed at a SQL server, and changes to Zope objects only take place on a development system, you can periodically copy the object repository file to each of the Zope servers and restart them. For more info, see http://www.zope.org/Products/ZEO Cheers, Evan @ 4-am & digicool
participants (2)
-
Bostick, Aaron -
Evan Simpson