DynamoDB uses eventually consistent reads, unless you specify otherwise. Read operations (such as GetItem, Query, and Scan) provide a ConsistentRead parameter. If you set this parameter to true, DynamoDB uses strongly consistent reads during the operation.
What is Eventual Consistency in DynamoDB?
Upasana | July 26, 2018 | 1 min read | 45 views
Eventual Consistency in DynamoDB
DynamoDB supports eventually consistent and strongly consistent reads.
Eventually Consistent Reads
When you read data from a DynamoDB table, the response might not reflect the results of a recently completed write operation. The response might include some stale data. If you repeat your read request after a short time, the response should return the latest data.
Strongly Consistent Reads
When you request a strongly consistent read, DynamoDB returns a response with the most up-to-date data, reflecting the updates from all prior write operations that were successful. A strongly consistent read might not be available if there is a network delay or outage.
Top articles in this category:
- AWS DynamoDB Java interview questions
- What are Conditional Writes in AWS DynamoDB
- What are Best Practices for Using Amazon DynamoDB?
- How will you ensure that no two threads update the same db record in parallel in amazon DynamoDB
- How to implement Atomic Counters in DynamoDB for high throughput
- Scan all records of a Amazon DynamoDB table using a Java Code
- How to automatically Retry DynamoDB Write on ProvisionedThroughputExceededException
Recommended books for interview preparation:
Find more on this topic:
No SQL design and development - Amazon DynamoDB, MongoDB, MySQL document DB.
Last updated 1 week ago