|
Wednesday 06 January 2010 2:17:32 am
Version:1.0 StartHTML:0000000167 EndHTML:0000002398 StartFragment:0000000449 EndFragment:0000002382 Hello Thank for the link to my blog. About Squid vs Varnish I think is a wrong way to compare both like that because each of them is the solution for a issue . Quickly this is my point of view. If you need a strong reverse proxy architecture with a high capacity, for many différent web sites or service, provided by different technology or cms you dont have a choice: you must use ICP for reduce the number of request to you php servers. If you need a strong reverse proxy architecture with a high capacity, for one web site provided by different technology or back office : you dont have a choice: you must use ESI for compose the page directly on the last stage; the revers proxy servers If you need a strong reverse proxy architecture with a high capacity, for one web site provided with a very high audience: you dont have a choice: you must use ESI for build the site on the static stage: reverse proxy .
- Varnish provide the ESI
- Squid 2.7 provide the ICP
- Squid 3 provide ICP and the ESI
You can imagine different solution:
- Use only one of them
- Use a stage of many squid, they exchanging their cache by ICP. front of of many single varnish server who compose the web page by ESI
- Use directly a stage of Squid 3.x servers
In my experience with eZ publish I was using a stage of many squid revers proxy v2.7 linked by ICP for the cache exchange. Behind them I had differentes php farm who provide different eZ publish web site. My 2ct
|
