Oracle GoldenGate Architecture Classic to Microservices Part -1
Oracle GoldenGate (OGG) is a tool used to copy data in real time from one database to another.
It works by reading database transaction logs and sending changes immediately to the target system.
GoldenGate is mainly used when businesses need high availability, real-time data, and zero downtime.
History of Oracle GoldenGate
1995: GoldenGate software was created
2009: Oracle acquired GoldenGate
21c: Last version that supports Classic Architecture
23c onwards: Only Microservices Architecture is supported
Why Do We Use Oracle GoldenGate?
Oracle GoldenGate is commonly used for:
Backup and Disaster Recovery
Auditing and Compliance
Real-time Reporting
Analytics systems
Load distribution (offloading reporting load from production)
Database migration with minimum downtime
Key Features of Oracle GoldenGate
Supports one-way, two-way, and multi-way replication
Can replicate data between multiple databases at the same time
Allows filtering and transforming data during replication
Supports both DML (Insert, Update, Delete) and DDL (Create, Alter, Drop)
Works with different database types, such as:
- Oracle
- SQL Server
- MySQL
- PostgreSQL
Types of Replication
1. Uni-Directional Replication (One-Way)
What it means:
Data moves only in one direction — from source to target.
Where it is used:
Reporting databases
Data warehouse
Disaster recovery
Example:
Production Database → Reporting Database
Changes made in the production database are copied to the reporting database.
2. Bi-Directional Replication (Two-Way)
What it means:
Data moves in both directions between two databases.
Where it is used:
Active-Active databases
High availability systems
Main challenge:
Same data may be updated in both databases
Conflict handling rules are required
Example:
Two regional databases update each other continuously.
3. Multi-Directional Replication (Multiple Systems)
What it means:
Data moves between many databases.
Where it is used:
Global companies
Multiple data centers
Challenges:
Design is complex
Must avoid data loops and conflicts
Example:
Databases in US, Europe, and Asia sharing data.
Oracle GoldenGate Architectures
1. Classic Architecture
This is the traditional GoldenGate setup.
Command-line based (GGSCI)
Simple and widely used
Supported until GoldenGate 21c
Components:
Extract: Captures changes from database logs
Local Trail: Stores captured data on source server
Data Pump: Sends data to target server
Remote Trail: Stores data on target server
Replicat: Applies changes to target database
2. Microservices Architecture
Introduced in GoldenGate 12.3, this is the modern architecture.
Main advantages:
Web-based user interface
REST API support
Better performance and scalability
Cloud and hybrid environment support
Supports non-Oracle databases from 21c
Services:
Service Manager: Controls all services
Administration Service: Used for configuration
Distribution Service: Sends data to targets
Receiver Service: Receives data from sources
Performance Metrics Service: Monitoring and statistics
GoldenGate Version Timeline
Up to 12.2 – Classic only
12.3 to 21c – Classic or Microservices
23c onwards – Microservices only
GoldenGate 21c – New Features
Automatic table capture with supplemental logging
Support for Autonomous Database
Improved DDL replication
Parallel Replicat for non-Oracle databases
Replication Flow (Classic Architecture)
Extract reads committed transactions from redo logs
Data is written to local trail files
Data Pump sends data to target system
Remote trail stores received data
Replicat applies changes to target database
Common Use Cases
Disaster recovery
Real-time reporting
Database migration
Data integration
Cloud and hybrid setup
Comments
Post a Comment