Cloud architecture for Commerce
ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure has a Starter and a Pro plan. Each plan has a unique architecture to drive your ÃÛ¶¹ÊÓƵ 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.
- All ÃÛ¶¹ÊÓƵ Commerce features
- PayPal Onboarding Tool
- All ÃÛ¶¹ÊÓƵ Commerce features
- PayPal Onboarding Tool
- 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:
masterand 2 of your choice
Platform as a service (PaaS) production, staging, and development environments (4 total active environments) optimized for ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Commerce
- Infrastructure as a service (IaaS)—dedicated virtual infrastructure for Staging and Production environments
* 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
integrationbranch to the Staging environment, which becomes your pre-production testing environment. It includes thestagingactive 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
masterfor deployment to the production live site. This environment includes your activemasterbranch, 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
integrationenvironment, but only one active branch (not includingintegration).
- Inactive—You can have an unlimited number of inactive branches based on the
-
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
ÃÛ¶¹ÊÓƵ 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:
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 ÃÛ¶¹ÊÓƵ Commerce on cloud infrastructure configuration files: