strongly consistent read
A database read guaranteed to return the result of every write that finished before it, never an older copy.
In more detail
DynamoDB reads are eventually consistent by default because each item is copied across availability zones. A strongly consistent read costs twice the read capacity and can have higher latency, so use it only where the freshest answer matters, such as checking a balance just written.
Related terms
- eventual consistency — A guarantee that copies of data will match once writes stop, even though a read straight after a write may briefly see an older value.
- Amazon DynamoDB — Amazon's fully managed key-value and document database, which stores items in tables without any servers for you to run.
- replication — Keeping copies of data in more than one place, updated automatically, so one failure does not lose or block it.
- consistency — The guarantee about whether what you read reflects what was most recently written.
- quorum — The minimum number of members, more than half, that must agree before a replicated system accepts a change.
- leader — The one replica that accepts writes and decides their order, which followers then copy.
Taught in
- Database Performance: Caches, Proxies And Capacity Units — AWS Certified Solutions Architect – Associate (SAA-C03) Exam Prep
- NoSQL and DynamoDB — Cloud Infrastructure & Hyperscaler Architecture
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Consistency, And The Truth About CAP — Scalable System Design & Distributed Architecture