hard20 pts · first answer countsdatabasesconsistencysystem-design

Profile shows old data after saving

Writes go to the primary and reads go to async read replicas. Users sometimes save their profile and see the old values on the next page load. What is a good fix?

A.Add a Redis cache in front of the replicasB.Add more read replicas so each one has less load and therefore replays changes from the primary fasterC.Use READ UNCOMMITTED on the replicasD.Route a user's reads to the primary for a short time after they write (read-your-writes)

Discussion 0

Join free to post in the discussion.

Profile shows old data after saving

Discussion 0

Related questions