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.
gefragt vor 3 Jahren633 Aufrufe
1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
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
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren