Re:Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze...
by ejdyksen on Thursday November 10, 2016 @02:01PM
(#12923167)
That is pretty old, considering what S3 has changed in the past two years. In particular, it talks about reading S3's us-standard region from the East and West coasts, and that has evolved to where us-standard (which is really us-east-1) is now the same as all other regions when it comes to consistency (presumably because all requests physically go to the East coast now, but I haven't tested that):
http://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction....
Re:Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze...
by gaul on Thursday November 10, 2016 @02:11PM
(#12923254)
Fair point, I will update the AWS us-standard results and include Backblaze as well.
Re:Show HN: Amazon S3, Microsoft Azure, Rackspace, Backblaze...
by finnh on Thursday November 10, 2016 @03:21PM
(#12923935)
Per that AWS page, you might want to add an asterisk that you lose read-after-write if you make a GET or HEAD to the keyname before your first PUT. So checking if the object exists will punk you down to eventual consistency.
https://github.com/andrewgaul/are-we-consistent-yet