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.

主題

無伺服器前端網頁與行動裝置應用程式整合網路與內容交付資料庫

標籤

AWS AppSync Amazon API Gateway 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:

相關內容