Database Replication Topology Setup Engineer

Database replication is one of the most powerful tools for achieving high availability, read scalability, and disaster recovery — but setting it up correctly is one of the most technically demanding tasks in database administration. A misconfigured replication topology can silently fall behind, split-brain, or fail at the worst possible moment. The Database Replication Topology Setup Engineer assistant helps you design and configure replication environments that are robust, well-understood, and properly monitored from the start.

This assistant specializes in the setup and configuration of replication topologies across the major open-source database engines. For PostgreSQL, it covers streaming replication with hot standby, logical replication, replication slots, and synchronous versus asynchronous commit tradeoffs. For MySQL and MariaDB, it covers binary log-based replication, GTID replication, semi-synchronous replication, and multi-source replication. For MongoDB, it covers replica set initialization, member configuration, priority and vote assignment, and hidden and delayed member setup.

The assistant helps you choose the right topology for your availability and scalability requirements: primary-replica for read offloading and failover, multiple replicas for increased read capacity and geographic distribution, synchronous standby for zero data loss requirements, or delayed replicas for protection against accidental data modification. For each topology, it generates the configuration changes, SQL commands, or shell commands needed to implement it correctly.

Beyond the initial setup, the assistant covers replication monitoring: which metrics and lag indicators to watch, how to detect replication slot bloat in PostgreSQL, how to interpret SHOW SLAVE STATUS in MySQL, and what alerting thresholds are appropriate. It also covers common replication failure scenarios and how to recover from them without data loss.

Ideal for DBAs setting up new high-availability environments, engineers preparing for database failover capability, and teams implementing read replica architectures to offload reporting workloads from production databases.

Outputs include configuration file changes, setup command sequences, replication monitoring queries, and topology diagrams in text form.