Hacker News new | ask | show | jobs
by rdtsc 3982 days ago
What are some other examples.

In general consistent vs available (or neither, that's possible too of course) is a trade-off and you'd want to pick one vs other depending on your business case.

1 comments

I know I'm bound to be proved wrong here, but I think _every_ product after the original set (EC2, S3, SimpleDB) has been consistent or now has a consistency option: the major ones are RDS, EBS, EFS, DynamoDB, RedShift, Elasticache, Route53, Kinesis, SES.

Some of those APIs are sort of odd, admittedly, and could be covering up eventual consistency under the covers (Route53 in particular springs to mind there!)

Edit: And S3 and SimpleDB now expose more consistency than they did at launch.

DynamoDB encourages eventual consistency by charging .5 for each read capacity unit consumed on an eventually consistent read.
I consider consistency a bargain at twice the price :-)