Consistency Flashcards
Eventually Consistent Reads
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
DynamoDB returns a response with the most up-to-date data, reflecting the updates from all prior write operations that were successful.
Strongly Consistent Reads Disadvantages
A strongly consistent read might not be available if there is a network delay or outage. In this case, DynamoDB may return a server error (HTTP 500).
Strongly consistent reads may have higher latency than eventually consistent reads.
Strongly consistent reads are not supported on global secondary indexes.
Strongly consistent reads use more throughput capacity than eventually consistent reads.