2 ms·
This immediately reminded me of the recent update to AWS S3 to provide strong read-after-write consistency, which Azure Storage Accounts do provide, but S3 hist
by jiggawatts 5y ago
This immediately reminded me of the recent update to AWS S3 to provide strong read-after-write consistency, which Azure Storage Accounts do provide, but S3 historically did not: 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...
It's these subtle (timing!) differences that might be documented somewhere, but aren't an explicit part of the API surface in any meaningful way. Programmers who naively assumed that blob store APIs are "all the same" and are "just" HTTP GET and PUT calls were in for a lot of fun surprises...
Programming theory has a long way to go before it can encode these kinds of subtleties in a way that it won't trip people up.