S3 strong consistency implications

Question

Hi,
A customer is claiming that the [S3 strong consistency](https://aws.amazon.com/s3/consistency/) claims contradict the [CAP theorem](https://en.wikipedia.org/wiki/CAP_theorem). So something had to be sacrificed.

He is asking what was sacrificed to get strong consistency.

Accepted Answer

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

S3 strong consistency implications

Conteúdo relevante