|
Wednesday 22 October 2008 1:57:36 pm
"1 master/N slaves is supported - but you'd better go with the latest version of eZ Publish, as there have been a few bugfixes in master/slave support lately." So far, the concerned project is based on eZ 4.0.0 - It is not yet planned to upgrade on 4.0.1 "depends on the kind of mysql cluster you can set up. Standard cluster iirc has the in-memory only engine plus a lot of limitations on the queries it can run, so it is unsuitable for eZ." I was thinking of the MySQL Cluster solution, as it is presented on MySQL site. It looks there is only one solution for this (or I missed something). It's a pity that eZ Systems do not state clearly that MySQL Cluster is not suitable with eZ Publish (Or I missed it too)
"I'd say separating db from webserver is surely the easiest way to scale (2 servers).
Then add a reverse proxy in front (3 servers)." It's not possible as I need a SSO authentification based on NTLM. If we set a proxy in front of the web servers, the authentification fails.
"For ha/disaster recovery, you can then set up a mirrored stack in the other datacenter.
Of course this takes in no account load balancing or massive increases in traffic, but is also simpler to set up." That's what I had more or less in mind. Having the whole system in both data center so that I can set up a round robin DNS for load balancing between the 2 web servers, and with a db server in each data center.
Thanks for your answer,
Nicolas
|
