S3 strong consistency implications

0

Hi, A customer is claiming that the S3 strong consistency claims contradict the CAP theorem. So something had to be sacrificed.

He is asking what was sacrificed to get strong consistency.

AWS
질문됨 3년 전633회 조회
1개 답변
0
수락된 답변

I would point out that concurrent applications still need to consider that Amazon S3 does not support object locking for concurrent writers. If you have multi-threaded or distributed applications that update the same object concurrently, readers might get the "old" object value for a period of time. This is very well explained in the docs: https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel

AWS
전문가
Luca_I
답변함 3년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠