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.

Deployment Architecture

Deployment Architecture

The following diagrams show sample deployment diagrams.

Load Balancer with API Gateway/SSI Terminator and Web Services

ECE Deployment R5.png

Load Balancer without a API Gateway/SSI Terminator

ECE Deployment_2.png

Reverse Proxy with API Gateway/SSI Terminator

ECE Deployment_3.png

Notes on the Deployment Architecture Diagrams

This is a reference deployment and does not necessarily represent how you should deploy Elastic Path. Your deployment architecture depends on your organization's specific requirements in terms of performance, reliability, and scalability. If you need assistance, contact your Elastic Path representative.

  • The Proxy Server shown above is necessary for handling the Cortex API's Cross-origin Resource Sharing requirement.
  • The HTTP Server shown above is recommended for increasing performance handling. The HTTP Server in this scenario is serving up the static files for the Cortex API