ERP reference architecture

Make room for operational growth.

Connect application services and job workers to a shared acceleration tier.

A starting design for customer-managed business operations.

See how the design fits together.

ERP architecture: three independent AcceleratorsBusiness users connect through App gateway to ERP services. ERP services connects through a redundant TCP load balancer to one of three active Accelerators in separate failure domains, then to the same ERP database. Each instance consumes database changes to maintain its local cache. Job workers also send database requests through the stable TCP endpoint.Private cloud networkBusiness usersApp gatewayERPservicesStable TCP endpointRedundant TCPload balancerHealth checksHealthy-node routingIndependent AcceleratorsZone AAccelerator AZone BAccelerator BZone CAccelerator CERPdatabaseSystem of recordLocal cache · Local CDC consumerJob workersApplication 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.
ERP architecture: three independent AcceleratorsBusiness users connect through App gateway to ERP services. ERP services connects through a redundant TCP load balancer to one of three active Accelerators in separate failure domains, then to the same ERP database. Each instance consumes database changes to maintain its local cache. Job workers also send database requests through the stable TCP endpoint.Private cloud networkBusiness usersApp gatewayERPservicesStable TCP endpointRedundant TCPload balancerHealth checksHealthy-node routingIndependent AcceleratorsZone AAccelerator AZone BAccelerator BZone CAccelerator CERPdatabaseSystem of recordLocal cache · Local CDC consumerJob workersApplication 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.

Application entry & services
ERP services and job workers both send database requests through the Accelerator tier.
ERP services
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 erp 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.

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.

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.