From ef3d4e506dab746b1d490e1692cf2c01260a146d Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Mon, 14 Dec 2020 22:46:12 +0000 Subject: [PATCH] Update README note on eventual consistency AWS promise read-after-write consistency now, but presumably non-AWS S3-compatible services are still eventually consistent. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 918d2c8..80fdefa 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ Generally S3 cannot offer the same performance or semantics as a local file syst * random writes or appends to files require rewriting the entire object, optimized with multi-part upload copy * metadata operations such as listing directories have poor performance due to network latency -* [eventual consistency](https://en.wikipedia.org/wiki/Eventual_consistency) can temporarily yield stale data([Amazon S3 Data Consistency Model](https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel)) +* non-AWS providers may have [eventual consistency](https://en.wikipedia.org/wiki/Eventual_consistency) so reads can temporarily yield stale data (AWS offers read-after-write consistency [since Dec 2020](https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-now-delivers-strong-read-after-write-consistency-automatically-for-all-applications/)) * no atomic renames of files or directories * no coordination between multiple clients mounting the same bucket * no hard links