strong consistency
Make the exact freshness and ordering guarantee explicit.
Use this when A permission revocation or inventory decision must not use an older acknowledged value.
without the term
“After an update succeeds, later reads must see it. State the exact guarantee and supported scope.”
with the term · How do you ask a model for strong consistency?
Specify the required strong consistency contract and scope. Test read-after-write and use an atomic update for this invariant.
What is strong consistency?
Strong consistency is an umbrella phrase; specify the required contract. A linearizable operation appears atomic between invocation and response and respects real-time order. Transaction serializability alone does not specify real-time ordering.
Why does strong consistency matter when vibe coding?
An agent can choose a strong read endpoint while leaving an unsafe read-then-write race.
How do you do strong consistency?
Identify the data scope and real-time ordering requirement. Use the supported consistent read or atomic conditional write. Check reads after acknowledged writes and overlapping updates.
What goes wrong with strong consistency?
A fresh read alone does not make a later write atomic; caches and unsupported indexes can change the read path.
Sources for this entry
- Gilbert and Lynch: Brewer’s conjecture
Impossibility of providing atomic consistency and availability under partitions in the asynchronous model.
- Amazon DynamoDB: Read consistency
Strongly consistent reads reflect successful prior writes within the supported read scope; eventual reads may lag.
- PostgreSQL: Transaction isolation
Isolation-level behavior in PostgreSQL; snapshot isolation can still allow serialization anomalies.
Sources checked . Source checks do not establish human editorial approval. How we check content.