DocumentationCommerceCommerce on Cloud Infrastructure Guide

Cloud architecture for Commerce

Last update: Fri Sep 15 2023 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • Admin
  • Developer

Adobe Commerce on cloud infrastructure has a Starter and a Pro plan. Each plan has a unique architecture to drive your Adobe Commerce development and deployment process. Both the Starter plan and the Pro plan architecture deploy databases, web servers, and caching servers across multiple environments for end-to-end testing while supporting continuous integration.

For comparison, each plan includes the following infrastructure features and supported products.

Starter
Pro
Core features
Infrastructure and deployment
  • Continuous cloud integration tools with unlimited users
  • Fastly Content Delivery Network (CDN), Image Optimization (IO), and added security with generous bandwidth allowances. The Web Application Firewall (WAF) service is available on production environments only.
  • New Relic APM (Performance Monitoring) on 3 branches: master and 2 of your choice
    Platform as a service (PaaS) production, staging, and development environments (4 total active environments) optimized for Adobe Commerce
  • Egress filtering (outbound firewall)
  • Continuous cloud integration tools with unlimited users
  • Fastly Content Delivery Network (CDN), Image Optimization (IO), and added security with generous bandwidth allowances. The Web Application Firewall (WAF) service is available on production environments only.
  • New Relic Infrastructure on Production + APM (Performance Monitoring) on staging and production. The Managed alerts policy for Adobe Commerce policy implements monitoring best practices to proactively notify you about application and infrastructure issues affecting site performance.
  • Platform as a service (PaaS) based Integration development environments (2 total active environments) optimized for Adobe Commerce
  • Infrastructure as a service (IaaS)—dedicated virtual infrastructure for Staging and Production environments
High-availability infrastructure
High availability architecture with a three-server setup in the underlying Infrastructure as a service (IaaS) to provide enterprise grade reliability and availability
Dedicated hardware
Isolated and dedicated hardware in the underlying Infrastructure as a service (IaaS) to provide even higher levels of reliability and availability
24x7 email support
24x7 monitoring and email support for the core application and the cloud infrastructure
24x7 monitoring and email support for the core application and the cloud infrastructure
A dedicated Customer Technical Advisor (CTA)
Dedicated technical account management for the initial launch period, starting with your subscription until your initial site launch
Add-ons*

* Available for an additional fee

Starter projects

The Starter plan architecture has four environments:

  • Integration—The integration environment provides two testable environments. Each environment includes an active Git branch, database, web server, caching, some services, environment variables, and configurations.

  • Staging—As code and extensions pass your tests, you can merge your integration branch to the Staging environment, which becomes your pre-production testing environment. It includes the staging active branch, database, web server, caching, third-party services, environment variables, configurations, and services, such as Fastly and New Relic.

  • Production—When code is ready and tested, all code merges to master for deployment to the production live site. This environment includes your active master branch, database, web server, caching, third-party services, environment variables, and configurations.

  • Inactive—You have an unlimited number of inactive branches.

Pro projects

The Pro plan architecture has a global master with three environments:

  • Integration—The integration environment provides a testable environment that includes a database, web server, caching, some services, environment variables, and configurations. You can develop, deploy, and test your code before merging to the Staging environment.

    • Inactive—You can have an unlimited number of inactive branches based on the integration environment, but only one active branch (not including integration ).

  • Staging—The staging environment is for pre-production testing and includes a database, web server, caching, third-party services, environment variables, configurations, and services, such as Fastly.

  • Production—The production environment includes a three-node, high-availability architecture for your data, services, caching, and store. Production is your live, public store environment with environment variables, configurations, and third-party services.

Supported software and services

Adobe Commerce on cloud infrastructure uses:

  • Operating system: Debian GNU/Linux
  • Web server: Nginx
  • Database: MySQL (MariaDB)
  • Content Delivery Network (CDN): Fastly CDN

You can configure the following services:

WARNING
Elasticsearch 7.11 and later is not supported for Adobe Commerce on cloud infrastructure. Adobe Commerce versions 2.3.7-p3, 2.4.3-p2, and 2.4.4 and later support the OpenSearch service. The on-premises installations continue to support Elasticsearch.
NOTE
See System requirements in the Installation guide for recommended versions.

The Fastly CDN module is used for CDN and caching services on staging and production environments. See Configure Fastly services.

For information about configuring the software versions to use in your implementation, see the following Adobe Commerce on cloud infrastructure configuration files:

recommendation-more-help
05f2f56e-ac5d-4931-8cdb-764e60e16f26