Announcement: You can find the guides for Commerce 7.5 and later on the new Elastic Path Documentation site. This Developer Center contains the guides for Commerce 6.13.0 through 7.4.1.Visit new site

This version of Elastic Path Commerce is no longer supported or maintained. To upgrade to the latest version, contact your Elastic Path representative.

Server clustering and load balancing

Server clustering and load balancing

Elastic Path supports load balanced server clusters for the storefront and the search server.

A server cluster is a group of computers acting as one server. A common use of clusters is to increase server performance and server availability. In a load balanced cluster, one server distributes work to the cluster nodes.

Common load balanced cluster components:

  • Load balancer – The server that handles all website traffic and distributes work to the cluster nodes.
  • Cluster nodes – The servers in the cluster that contain an instance of a website application (for example, a storefront) and perform the work.
  • File synchronization server – The server that synchronizes changes to common files across all the servers in the cluster.

Elastic Path can run on a load balanced cluster. A typical configuration includes:

  • Load balancer – An Apache server configured with a load balancing module.
  • Cluster nodes – Multiple application servers in a cluster, each with the Elastic Path storefront deployed on it.
  • Commerce Manager server – An application server with an Elastic Path Commerce Manager deployment.
  • Search server – An application server with the Elastic Path Search Server deployed on it.
  • File synchronization server – An rsync server on the Commerce Manager server and an rsync client on each cluster node.
Note: Important

The following sections are only meant to be a guide. Experience in server clustering and load balancing is recommended to perform these steps.