GDS Use Case Summary

Review different use case scenarios to better understand how you can ptimize database availability, performance, and scalability by intelligently managing workloads across replicated and distributed environments.

Table 5-1 Ensuring Business Continuity with Automated Database Failover

Database Architecture	Replication Technology	Workload	Workload Dynamics
Active-Active	Oracle GoldenGate	read-write	In an active-active configuration, read-write (and read-only) workloads can run both on replicas, or be assigned to separate replicas. If a database fails,then its workloads automatically transition to the surviving replica. Some customers configure Oracle GoldenGate replicas solely for failover, without running workloads on them.
Active-Active	Oracle GoldenGate	read-only	Read-only workloads can run on both primary and replicas, or be assigned separately. If a database fails, then read-only workloads seamlessly transition to the surviving replica while maintaining service availability.
Active-Passive	Oracle GoldenGate	read-write	Read-write workloads are always processed on the primary database. If the primary fails, then the standby takes over as the new primary, and read-write workloads automatically transition to it.
Active-Passive	Oracle Active Data Guard	read-only	The standby database can optionally handle read-only workloads under normal conditions. On primary failure, the standby assumes the primary role and serves both read-write and read-only workloads.

Table 5-2 Minimizing Resource Requirement with Intelligent Load Balancing

Database Architecture	Replication Technology	Workload	Workload Dynamics
Active-Active	Oracle GoldenGate	read-write	In an active-active setup, read-write workloads can be processed on both replicas or distributed based on workload type. Read-write services can be configured to balance traffic dynamically across available replicas.
Active-Active	Oracle GoldenGate	read-only	Read-only workloads can run on both replicas or be distributed independently of read-write workloads. Read-only services can be configured to distribute queries optimally across multiple replicas for better performance.
Active-Passive	Oracle Active Data Guard	read-write	In an active-passive setup, read-write workloads are processed only on the primary database. If the primary is an Oracle Real Application Clusters (Oracle RAC) database, then workloads can be distributed across the Oracle RAC nodes, but they are not balanced across multiple databases.
Active-Passive	Oracle Active Data Guard	read-only	One or more standby databases can be used to offload read-only workloads from the primary. If multiple standby databases exist, then read-only workloads can be load-balanced among them (for example using a reader farm configuration).

Table 5-3 Geo-Aware Workload Routing for Faster Response Times

Database Architecture	Replication Technology	Workload	Workload Dynamics
Active-Active	Oracle GoldenGate	read-write	In an active-active setup, regional read-write workloads can be serviced by local (regional) database replicas. Alternatively, both read-write and read-only regional workloads can be processed locally or uniformly across replicas.
Active-Active	Oracle GoldenGate	read-only	In an active-active setup, regional read-only workloads can be serviced by local (regional) database replicas. Alternatively, both read-write and read-only regional workloads can be processed locally or uniformly across replicas.
Active-Passive	Oracle Active Data Guard	read-write	Regional affinity does not apply to read-write workloads in an active-passive setup. Read-write workloads are always processed on the primary database, regardless of its region.
Active-Passive	Oracle Active Data Guard	read-only	In a multi-standby environment (for example, a reader farm), read-only workloads can be processed on a regional standby database to optimize performance and reduce latency.

Table 5-4 Improving Read Performance with Smart Replication Lag Aware Routing

Database Architecture	Replication Technology	Workload	Workload Dynamics
Active-Active	Oracle GoldenGate	read-write	Does not apply.
Active-Active	Oracle GoldenGate	read-only	In a single-replica setup, read-only workloads are served at the replica as long as the replication lag remains within the configured threshold. If the lag exceeds the threshold, then the workload is failed over to the primary. In a multi-replica configuration, read-only workloads are redirected to another replica within the acceptable replication lag limit. If no replicas meet the threshold, then the workload is routed to the primary database.
Active-Passive	Oracle Active Data Guard	read-write	Does not apply
Active-Passive	Oracle Active Data Guard	read-only	In a single-standby configuration, read-only workloads are served at the standby as long as the replication lag remains within the allowed threshold. If the threshold is exceeded, then the workload is redirected to the primary. In a multi-standby setup, the workload is transitioned to another standby within the acceptable replication lag limit. If no standbys meet the threshold, then the workload is routed to the primary database.

Table 5-5 Boosting Query Speed with Ultra-Fast Cache

Database Architecture	Replication Technology	Workload	Workload Dynamics
Active-Passive	Oracle True Cache	read-write	The primary database processes both read-write and read-only workloads. However, all or specific read-only workloads can be offloaded to Oracle True Cache to improve performance.
Active-Passive	Oracle True Cache	read-only	Oracle True Cache processes read-only workloads, either fully or selectively, based on configured services. This reduces load on the primary database and enhances query response times.

Parent topic: Using Global Data Services (Architectures, Use Cases, Application Development)