Scalability and capacity planning

This section provides technical recommendations for scaling Adobe Commerce environments to prepare for high-traffic events such as the holiday season.

Plan cluster upsize early (Cloud only) plan-cluster-upsize-early

For Commerce on cloud infrastructure customers, a temporary cluster upsize allocates more computing resources to handle peak-season traffic surges. Raise a support ticket in advance with the date range and required cluster size, and coordinate with your dedicated Account Manager on current resource consumption and requirements. Submit the request at least 48 business hours before the capacity is needed—for the holiday season specifically, submit as early as possible, since capacity during Black Friday and Cyber Monday is limited. See How to request a temporary upsize.

For example, a Pro-architecture customer with a daily baseline of 24 cores (24 vCPUs, 96 GB RAM) upsizing to 96 cores for 7 days would use roughly 4 times the resources (96 vCPUs, 384 GB RAM)—an incremental consumption of about 504 vCPU-days (96×7 − 24×7).

Fastly origin shielding fastly-origin-shielding

The purpose of Adobe Commerce Fastly’s origin shielding is to reduce traffic directly to the Adobe Commerce origin. When a request is received, a Fastly edge location (Point of Presence) checks for cached content and delivers it. If it isn’t cached, it continues to the Shield POP to check if it’s cached there—if the content has previously been requested even from another global POP, it will be cached. Finally, if it isn’t cached on the Shield POP, it will only then proceed to the origin server.

Fastly origin shielding can be enabled in the Adobe Commerce Admin, in the Fastly configuration backend settings. Choose a shield location closest to your Adobe Commerce origin data center for the best performance. For details, see Configure back ends and origin shielding. By default, Fastly origin shielding is not enabled.

Conduct load and failover tests conduct-load-and-failover-tests

Perform load and recovery tests before major campaigns to validate scaling configurations and rollback plans.