-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I have some years(?) experience with Cherokee now, I know if I don't
develop anything keeps on running, and is usually (always ;) a good
choice to implement on a mission critical application.
Currently for a new website someone asked for a specific load-balancing
technique. Which I think in Cherokee terms is easy to solve:
[Cherokee Server]
/ \
[fcgi-php] [fcgi-php]
[ server ] [ server ]
This probably scales well. But now; what if you a priori know:
1) One Brave Chief cannot handle the load due to heavy SSL
2) The amount of traffic to one machine is just too much
3) If failing = big problems
I wonder what the users here would choose. Would you go with something
like LVS, or would you take another balancing approach?
Stefan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEAREKAAYFAkjlAL8ACgkQYH1+F2Rqwn2SqgCfXPlhl+cMgQUBOymtXfnbqijS
VWAAnjk8xcrQOF06k3cpZGtctknricn5
=2jsT
-----END PGP SIGNATURE-----
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
