This topic describes a generic recommended setup for Adobe Commerce and Magento Open Source instances using plain servers hosted physically in a data center (not virtualized) in which resources are not shared with other users. Your hosting provider, especially if it specializes in Commerce high performance hosting, might recommend a different setup that is equally or more effective for your requirements.
For Adobe Commerce on cloud infrastructure environments, see Starter architecture.
The Commerce Reference Architecture diagram represents the best practice approach to set up a scalable Commerce site.
The color of each element in the diagram indicates whether the element is part of Magento Open Source or Adobe Commerce and if it is required.
The following sections provide recommendations and considerations for each section of the Commerce Reference Architecture diagram.
Magento supports several full page caching engines (File, Memcache, Redis, Varnish) out of the box, along with expanded coverage through extensions. Varnish is the recommended full page cache engine. Commerce supports many different Varnish configurations.
For sites that do not require high availability, we recommend using a simple Varnish setup with Nginx SSL termination.
For sites that require high availability, we recommend using a 2-tier Varnish configuration with an SSL terminating load balancer.