You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DynamoDB cache is great for many reasons, but there is small side-effect that might or might not be visible for the users. The DynamoDB default reading mode is "Eventually Consistent". DynamoDB can also be used in "Strongly Consistent" read mode, if you specify that when getting data.
E.g.
Write data to cache
Read data from cache
If 2nd step is not able to read always data from cache that 1st step wrote, it is usually a big problem e.g. with session. This consistent read might fail and if it fails, fall back to normal read is recommended.
The DynamoDB cache is great for many reasons, but there is small side-effect that might or might not be visible for the users. The DynamoDB default reading mode is "Eventually Consistent". DynamoDB can also be used in "Strongly Consistent" read mode, if you specify that when getting data.
E.g.
If 2nd step is not able to read always data from cache that 1st step wrote, it is usually a big problem e.g. with session. This consistent read might fail and if it fails, fall back to normal read is recommended.
https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ReadConsistency.html
What do you think? Is this something that could maybe be parametrised setting for the DynamoDB cache like TTL field?
The text was updated successfully, but these errors were encountered: