The diagram showcases an example deployment architecture spanning two regions: East and West. Each of the three database pools is spread across both regions and demonstrates unique deployment setups using a combination of GoldenGate Replicas, Active Data Guard Standbys, and True Caches. The Global Service Managers, GSM-EAST and GSM-WEST act as remote listeners for all databases in the Global Data Services configuration and route connection requests to the most appropriate endpoint based on routing strategies such as geographical location, load balancing, role, replication lag, and service availability.

The topmost database pool has a primary database that supports Read-Write (RW) workloads, with a True Cache and an Active Data Guard Standby in each region to handle Read-Only (RO) workloads. True Cache reads from the primary database to warm up the cache or when there is a cache miss. Once a block is cached, it is updated automatically through redo apply from the primary database. Applications are configured so that frequent reads go to the True Caches, while writes and infrequent reads go to the primary database. The Active Data Guard Standby in each region provides disaster protection and high availability, while also reducing the load on the primary production database by supporting Read-Only workloads.

The middle database pool has a primary database supporting RW workloads with a GoldenGate Replica in each region that supports both Read-Write and Read-Only workloads. The Active Data Guard Standby in each region provides disaster protection and high availability, while also reducing the load on the primary production database by supporting Read-Only workloads.

The bottom database pool has a primary database supporting RW workloads, with a True Cache, GoldenGate Replica, and Active Data Guard Standby in each region offering enhanced query response times, disaster protection, and reduced load on the primary database.

GDS Deployment: High Level Steps