---
title: "Comment by Abhinav Sharma on \"System Design Drill Day 4: Read Replicas and Replication Lag\" | Hashnode"
description: "The empty My Orders page right after checkout is the textbook read-your-writes failure. Sending the reads that follow a write to the primary for a short window"
url: "https://hashnode.com/posts/system-design-drill-day-4-read-replicas-and-replication-lag/6ad97f46fe6584e965eff0fc/comment/6ad998a4217fe726b407a2db"
---

[Discussion](https://hashnode.com/posts/system-design-drill-day-4-read-replicas-and-replication-lag/6ad97f46fe6584e965eff0fc)

Comment [System Design Drill Day 4: Read Replicas and Replication Lag](https://hashnode.com/posts/system-design-drill-day-4-read-replicas-and-replication-lag/6ad97f46fe6584e965eff0fc)

[Abhinav Sharma](https://hashnode.com/@abhinavs1920)

[Oct 22](https://hashnode.com/posts/system-design-drill-day-4-read-replicas-and-replication-lag/6ad97f46fe6584e965eff0fc/comment/6ad998a4217fe726b407a2db)

The empty My Orders page right after checkout is the textbook read-your-writes failure. Sending the reads that follow a write to the primary for a short window is usually cheaper than making the whole app strongly consistent.

[Anish Ansari](https://hashnode.com/@anish78)

[Oct 22](https://hashnode.com/posts/system-design-drill-day-4-read-replicas-and-replication-lag/6ad97f46fe6584e965eff0fc/comment/6ad998a4217fe726b407a2db#reply-6ad9b8d9e144ae2b2e05dad0)

Thanks Abhinav, that empty My Orders page is exactly the bug that makes people think their order failed. Pinning reads to the primary for a few seconds after a write fixes it without paying for strong consistency everywhere.
