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 아마존 API 게이트웨이 아마존 DynamoDB 아마존 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:

관련 콘텐츠