After a cashier posts a fee, the next read of the resident balance…

Question

After a cashier posts a fee, the next read of the resident balance on another path sometimes shows the old amount when using eventually consistent reads. Staff need the latest balance immediately. What should the developer select?

Accepted Answer

Use strongly consistent reads for the balance lookup when the workflow cannot tolerate staleness, accepting the consistency tradeoffs. — Eventual consistency is like a receipt that has not hit every branch copy yet—cashiers can see yesterday’s balance for a moment. When the counter needs the truth right now, ask DynamoDB for a strongly consistent read.

Answer

Cache balances only in the cashier browser and never re-read DynamoDB after a write.

Answer

Use a full table Scan with eventual consistency and display whichever item returns first.

Answer

Stop accepting fee payments so read-after-write staleness cannot occur.

After a cashier posts a fee, the next read of the resident balance on another path sometimes shows the old amount when using eventually consistent reads. Staff need the latest balance immediately. What should the developer select?

Short Explanation

Full Explanation