gaul / are-we-consistent-yet Goto Github PK

us-standard is a logical region comprised of two physical regions, northern Virginia and Pacific Northwest:

http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region

Amazon partially documents that you can connect to the former physical endpoint but actually exposes two physical endpoints:

• s3-external-1.amazonaws.com
• s3-external-2.amazonaws.com

AWCY could measure the difference in eventual consistency when using either the same endpoint or different ones.

Amazon clarified their consistency model:

https://docs.aws.amazon.com/AmazonS3/latest/dev/Introduction.html#ConsistencyModel

Note that read-after-write is more complicated if you read-after-write-after-read, according to a Hacker News comment:

https://news.ycombinator.com/item?id=12922048

Thanks for making this. It's super interesting. Although it appears you're using one byte payloads...is this correct? If so, it seems like that makes this merely a theoretical exercise since in "real world" usage payloads would almost always be way, way bigger. I would think the larger the payload the greater the chance for there to be consistency issues. Unless I am missing something it seems like ideally you'd have multiple tables in your README using different payload sizes. Thoughts?

jclouds does not presently support this.

See https://forums.aws.amazon.com/message.jspa?messageID=165770#165919

Some providers have small eventual consistency windows such that latency between the client and the object store could mask any consistency issues.

along the lines of #6, it'd be nice to add amazon dynamodb too. details: http://aws.amazon.com/dynamodb/faqs/#Read_Consistency

(...and maybe also simpledb? http://aws.amazon.com/simpledb/faqs/ , search for 'read consistency'.)

This would better match the Mozilla are-we-*-yet sites.

BackBlaze B2 might be a good candidate to include in this analysis.

Based on the latest Google's and Amazon's documentation buckets support offers strongly consistent.

great project idea, nice work!

i'd love to see the google app engine datastore added. details: https://cloud.google.com/appengine/docs/python/datastore/ , https://cloud.google.com/appengine/docs/python/datastore/queries#Python_Data_consistency

i may eventually tackle this myself and send a PR. i'll post if i start so we don't collide.

https://aws.amazon.com/about-aws/whats-new/2020/12/amazon-s3-now-delivers-strong-read-after-write-consistency-automatically-for-all-applications/

In the References section, the following link appears to be broken (not working) because opening it shows Error 404 (Not Found):

Eventual Consistency: How soon is eventual?