EngineGrids

CMS reference architecture

A faster CMS. More room to grow.

Support growing audiences while getting more from your database infrastructure.

A cloud deployment pattern for customer-managed content platforms.

Discuss a deployment kitExplore Performance Lab

See how the design fits together.

CMS architecture: three independent AcceleratorsVisitors connect through CDN / WAF to CMS application. CMS application connects through a redundant TCP load balancer to one of three active Accelerators in separate failure domains, then to the same Content database. Each instance consumes database changes to maintain its local cache. Media goes directly from the CMS application to object storage.Private cloud networkVisitorsCDN / WAFCMSapplicationStable TCP endpointRedundant TCPload balancerHealth checksHealthy-node routingIndependent AcceleratorsZone AAccelerator AZone BAccelerator BZone CAccelerator CContentdatabaseSystem of recordLocal cache · Local CDC consumerMedia object storageMediaApplication traffic through an external TCP load balancer
Independent Accelerators behind an external TCP load balancer. Each instance maintains its local cache from database CDC. Health checks route new connections to healthy nodes; failed sessions reconnect.
CMS architecture: three independent AcceleratorsVisitors connect through CDN / WAF to CMS application. CMS application connects through a redundant TCP load balancer to one of three active Accelerators in separate failure domains, then to the same Content database. Each instance consumes database changes to maintain its local cache. Media goes directly from the CMS application to object storage.Private cloud networkVisitorsCDN / WAFCMSapplicationStable TCP endpointRedundant TCPload balancerHealth checksHealthy-node routingIndependent AcceleratorsZone AAccelerator AZone BAccelerator BZone CAccelerator CContentdatabaseSystem of recordLocal cache · Local CDC consumerMedia object storageMediaApplication traffic through an external TCP load balancer

More application capacity

Serve more application queries across multiple Accelerators.

Less database demand

Reduce repeated database work as application traffic grows.

More from your investment

Connect capacity planning to infrastructure and licensing value.

A clear role for every layer.

Delivery & media
CDN, application protection, and object storage support content delivery.
CMS application
Application services connect through a stable database endpoint.
Accelerator tier
Independent Accelerators with routing to healthy nodes. Each instance keeps a local cache and consumes database changes through CDC.
Database tier
The content database remains the system of record. Database availability is managed separately.

Plan your deployment.

  • Choose the cloud and database engine.
  • Size the application and Accelerator tiers for demand.
  • Plan access, monitoring, and operating responsibilities.
Read the deployment overview

Your deployment resources.

Discuss Terraform and deployment resources Setup and configuration guide Administrator guide

Connect the design to customer value.

Use Performance Lab to compare application response, database demand, and capacity with the customer’s workload.

Open Performance LabDiscuss this designHow to buyWhere to buy
All reference architectures

Analytics preferences

Google Analytics helps us understand use of our public pages. It is optional. The website and inquiry forms work whether you accept or decline.

Your choice applies to this browser. You can change it here at any time. See our Privacy Policy for details.