replication-strategies

Design PostgreSQL and MySQL replication strategies with failover runbooks.

Updated Mar 29, 2026

Search Tags:#postgresql #replication #failover #mysql #read-replica #database-replication #lag-monitoring

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill replication-strategies

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: replication-strategies
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/replication-strategies
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill replication-strategies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing and implementing reliable database replication strategies to balance availability, consistency, and performance across primary and replica nodes.

Core Features & Use Cases

Choose replication modes (asynchronous, synchronous, semi-synchronous) to meet RPO/RTO needs.
Implement read routing and query offloading to replicas to scale reads while preserving correctness.
Monitor replication lag, slot health, and failover readiness with alerting.
Plan, test, and automate failover and promotion procedures, including fencing practices.
Manage WAL/LAG considerations for PostgreSQL and binlog for MySQL, including slot management.
Use cases: high-availability deployments, cross-region replication, and read-intensive workloads.

Quick Start

Configure your database with the chosen replication mode and routing rules, then enable lag monitoring and failover readiness.

Frequently Asked Questions about replication-strategies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What are the best database replication strategies for balancing availability and consistency?▼

Database replication strategies balance availability and consistency by selecting appropriate replication modes like asynchronous, synchronous, or semi-synchronous to meet specific RPO/RTO requirements across primary and replica nodes.

How do I monitor PostgreSQL replication lag and slot health?▼

Monitor PostgreSQL replication lag and slot health by tracking WAL generation rates and replication slot activity. This ensures replica nodes remain synchronized and alerts you to failover readiness or slot retention issues.

Does this support configuring read routing for MySQL read-replica deployments?▼

Yes, it supports MySQL read-replica deployments by implementing read routing and query offloading to replicas. This scales read-intensive workloads while preserving correctness and managing binlog replication lag.

When should I use synchronous vs asynchronous replication for cross-region failover?▼

Use synchronous replication for cross-region failover when strict zero data loss is required, and asynchronous replication when prioritizing high availability and lower latency over immediate consistency.

How do I automate database failover and promotion procedures safely?▼

Automate database failover and promotion safely by planning, testing, and automating procedures with proper fencing practices. This prevents split-brain scenarios and ensures reliable high-availability transitions.