hard20 pts · first answer countsdatabase-replicationconsistency

Saved profile shows old data

Writes go to the primary database and reads go to a read replica. After a user saves their profile and is redirected, the page often shows the old values for a second. What is the best targeted fix?

A.Make every replica synchronous, so no read anywhere can ever return data older than the primaryB.Add an index on the users tableC.Increase the cache TTL on the profile pageD.Read-your-writes: send that user’s reads to the primary briefly after a write

Discussion 0

Join free to post in the discussion.

Saved profile shows old data

Discussion 0

Related questions