Data Data Replication

Purpose

Design robust database replication architectures for high availability, disaster recovery, read scaling, and multi-region deployments. Covering master-slave, multi-master, and active-active topologies, with conflict resolution strategies and cross-region consistency models.

Agent Protocol

Trigger

Exact user phrases: "database replication", "multi-master", "active-active", "cross-region replication", "GoldenGate", "log shipping", "read replica", "synchronous replication", "asynchronous replication", "conflict resolution", "database mirroring", "always on", "data guard", "replica set", "DR plan", "disaster recovery".

Input Context

Before activating, verify:

• Database engine (MySQL, PostgreSQL, Oracle, SQL Server, MongoDB, Cassandra)
• Replication topology desired (master-slave, multi-master, active-active)
• Consistency requirements (RPO in seconds, RTO in minutes)
• Network latency between regions
• Write volume (TPS) and read ratio
• Conflict potential (multiple writers to same records)
• Existing infrastructure (cloud provider, peered VPCs, VPN, dedicated link)