Replication lag is the delay between a change being committed on a primary database and becoming visible on a replica. Read replicas increase capacity for read-heavy workloads, but replicas can fall behind by milliseconds or seconds under load. section 5.4.2
Replication strategy creates a direct trade-off:
- Synchronous replication waits for replica confirmation, minimizing lag while adding latency to every write. section 5.4.2
- Asynchronous replication lets the primary continue immediately, improving write performance while allowing replicas to fall behind. section 5.4.2
- Treat read-your-writes operations carefully: a user may update data on the primary and then receive stale data from a replica. section 5.4.2 section 5.4.4
A profile update that appears to vanish
A user updates their profile, then immediately views it. If the follow-up read goes to a replica that has not received the update, the change appears to disappear. Route such reads appropriately or accept eventual consistency only where the delay is acceptable. section 5.4.2
Measure lag under normal conditions and peak load, then relate it to user expectations. Audit read routing, connection counts, pool utilization, and database statistics before deciding whether replicas, write scaling, or another database pattern addresses the bottleneck. section 5.4.4





