Clustering in eZ Platform refers to setting up your install with= several web servers for handling more load and/or for failover.
Intro: Server setup overvie= w
This diagram illustrates how clustering of eZ Platform is typically set = up, the parts illustrate the different roles needed for a successful cluste= r setup. The number of web servers, Memcached servers, Solr servers, Varnis= h servers, Database servers, NFS servers, as well as whether some servers p= lay several of these roles (typically running Memcached across the web = server) is up to you and your performance needs.
The minimal requirements are the following (with what is currently supported in parentheses):
- Shared HTTP cache (using Varni= sh)
- Shared Persistence cache and Sessions (using Memcached)
- Shared Database (using MySQL/M= ariaDB)
- Shared Filesystem (using NFS, = or experimentally also S3)
For further details on requirements, see Requirements doc.
While this is not a complete list, further recommendations include:
- Using Solr for better sear= ch and better search performance
- Using a CDN for improved performance and faster ping time worldwide
- Using Active/Passive Database for failover
- In general: Make sure to use later versions of PHP and MySQL/MariaDB wi= thin what is supported for yo= ur eZ Platform version to get more performance out of each server.
Steps to set up Cluster
To set up Cluster you'll need to:
- Set up DFS Cluster which moves binary files to NFS
- Configure = Persistence Cache to use Memcached
- Set up Varnish, disable = Symfony HTTP Cache and set up cache invalidation to purge Varnish cache
- Configure sessions to use a cl= uster safe sessions handling
It is also highly recommended to set up Solr Bundle to be able to get better search and query per= formance, be able to scale it and offload database.