It's called "read-after-write consistency". Write-through cache is one way, or just use a strongly consistent database, haha. https://avikdas.com/2020/04/13/sc

It's called "read-after-write consistency". Write-through cache is one way, or just use a strongly consistent database, haha. https://avikdas.com/2020/04/13/scalability-concepts-read-after-write-consistency.html https://avikdas.com/2020/04/13/scalability-concepts-read-aft... https://en.wikipedia.org/wiki/Cache_%28computing%29#Writing_policies https://en.wikipedia.org/wiki/Cache_%28computing%29#Writing_... https://cloud.google.com/blog/products/databases/why-you-should-pick-strong-consistency-whenever-possible https://cloud.google.com/blog/products/databases/why-you-sho...