Magento Commerce Cloud architecture

Magento Commerce Cloud has a Starter and a Pro plan. Each plan has a unique architecture to drive your Magento 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.

	Starter	Pro
Core features	All Magento 2 core features PayPal Onboarding Tool Business Intelligence	All Magento 2 core features PayPal Onboarding Tool Business Intelligence B2B module
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 Blackfire.io Enterprise (Performance Testing) Platform-as-a-service (PaaS) based Production, Staging, and development environments (4 total active environments) optimized for Magento Commerce	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. Adobe-generated alert policies implement monitoring best practices to proactively notify you about application and infrastructure issues affecting site performance. Blackfire.io Enterprise (Performance Testing) Platform-as-a-service (PaaS) based Integration development environments (8 total active environments) optimized for Magento Commerce Infrastructure-as-a-Service (IaaS)—dedicated virtual infrastructure for Production environments and for Staging 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 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
Dedicated Technical Account Manager		Dedicated technical account management for the initial launch period, starting with your subscription until your initial site launch
Add-ons*	B2B module

* Available for an additional fee

Starter projects

The Starter plan architecture has four environments:

Integration—The Integration environment provides three testable environments. Each environment includes an active Git branch, database, web server, caching, services, environment variables, and configurations.
Staging—As code and extensions pass your tests, you can merge your Integration branch to a Staging environment, which becomes your pre-Production testing environment. It includes the staging active branch, database, web server, caching, 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.

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.
Staging—The Staging environment is for pre-Production testing and includes a database, web server, caching, 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.

Jan 16th, 2020