Start With One Copy

With one database there's nothing to be inconsistent with. Every read sees the last write, and a transaction is all the guarantee you need. Consistency becomes a question the day you make a second copy of the data: a read replica, a cache, another region. From then on a read can come from a copy that hasn't heard the news yet.

So the skill isn't picking the strongest model. It's deciding, for each operation, how fresh the answer has to be, and paying for strength only where being wrong costs something. The table above lists the signals in the order most systems meet them. This article gives you the vocabulary first, then the answer to each situation and a way to check it.

If users see stale or conflicting data
  • You used "eventual consistency" as an excuse for a bug
  • You can't explain the difference between linearizable and serializable
  • You read your own write and saw the old value, and assumed the cache was broken
  • Your Cosmos DB account is set to "Strong" everywhere because "safer"

This is the consistency menu — what each model actually guarantees, what it costs, and how to match it to your workload.