This website uses cookies to ensure you get the best experience.
Learn more.
A read replica falls behind during a write surge. The application serves stale data from the replica. Which approach best fits?
Published
- Bound application connection pools and assess a suitable pooling strategy.
- Inspect query plans and supported Query Insights diagnostics.
- Monitor replication lag and route freshness-critical reads to an appropriate consistent source.
- Coordinate credential version rollout, client refresh, and retirement of the old credential.
Comments — 0
Sign in to comment