Interesting to see ElasticSearch's decision to give up on partition tolerance validated

ElasticSearch gives up on partition tolerance in the CAP tradeoff, which is unique among NoSQL stores. Most NoSQL datastores readily give up on consistency to achieve availability and partition tolerance. The Basically Available, soft state, eventually consistent model, which was discussed in the context of banking on High Scalability is nice, but gives up so much to achieve partition tolerance. While ATMs can be partitioned often, the fact is that most consumer applications do not need to have such strict partition tolerance.

Looks like a few peeps are coming around to the idea: Dynamo Sure Works Hard

For more, check out Shay Banon's mailing list response on why ElasticSearch gives up on partition tolerance