2 ms·
> 2. S3 API and POSIX file IO aren't that different. They certainly aren't dealing with radically different concepts. The differences are more to do with the di
by yencabulator 3y ago
> 2. S3 API and POSIX file IO aren't that different. They certainly aren't dealing with radically different concepts. The differences are more to do with the difficulties of supporting the full featureset in a distributed and performant manner.
They are hugely different. S3 does not allow you to overwrite data in the middle of an object, while that's a significant use case for POSIX file APIs. S3 does not give you strongly consistent operations, while that's a significant use for POSIX file APIs.
- erik_seaberg 3y agoOriginally not, but they advertise strong read-after-write consistency as of December 2020. https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-read-after-write-consistency/ https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-rea...
- yencabulator 3y agoAs far as I know, you still don't get e.g. create-if-not-exist. The object listing is now strongly consistent, but you don't get to do atomic operations on it.