Cloudfront cache mutation:

Can anyone tell me the best practice of caching in cloudfront? Why mutation in the dynamodb table isn't reflecting? I have set the cache behaviour to max TTL:3sec, min TTL:0sec. When I'm refreshing the cloudfront url after 3 sec it is showing the mutation. But in the second refresh after 3 sec it is showing the older result.

主题

无服务器前端 Web 和移动应用程序集成网络和内容交付数据库

标签

AWS AppSync 亚马逊 API 网关 Amazon DynamoDB Amazon CloudFront 缓存

语言

English

Amplify_lover

已提问 2 年前220 查看次数

1 回答

最新
投票最多
评论最多

这些答案有用吗？为正确答案投票，以帮助社区从您的知识中受益。

已接受的回答

Are you doing strongly-consistent reads rather than eventually-consistent reads in DynamoDB? If not, then after a mutation a sequence of reads may return a mix of old and new values until full consistency is achieved.

专家

skinsman

已回答 2 年前

Amplify_lover
2 年前
I want something like when any mutation occurs it should pass through cloudfront to dynamoDB. When a mutation will occur cloudfront will match the ID of objects in cache, if id matches it will be updated in CloudFront and then in DynamoDB.

Cloudfront cache mutation:

相关内容