Why does MySQL replication lag under heavy writes?
Traditionally replicas apply changes from the primary's log on a single thread, so a replica cannot absorb writes as fast as a busy primary produces them, and falls behind. Lag means stale reads. Parallel apply and priming the replica's cache with rows the next writes will touch both help.
Answered in
Scaling MySQL Without Leaving MySQL: A Proxy Layer for Pooling, Routing and SafetyReplica reads, replication lag and cache priming, sharding without app rewrites, query guards and automatic failover, as a MySQL scaling layer provides them.
Read the full analysisOther questions this article answers
More system design & architecture questions
- How much spare capacity should a gateway keep?
- Why are bounded queues important for availability?
- Should a load balancer always move requests away from an unhealthy server?
- Can a circuit breaker prevent every cascading failure?
- Why does pagination improve API performance beyond just 'smaller responses'?
- Why is asynchronous logging faster than writing logs synchronously?
- When does caching actually help API performance, and when doesn't it?
- Why does payload compression trade CPU time for network time, and when is that worth it?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the System Design & Architecture beat.