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.
已提問 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 官方已更新 2 年前
