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 server, 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.
|Infrastructure and deployment||
|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 setup 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|
* Available for an additional fee
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 can have an unlimited number of inactive branches.
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.
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. This is your live, public store environment with environment variables, configurations, and third-party services.
Adobe Commerce on cloud infrastructure uses:
You can configure the following services:
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: