Michael Stonebraker weighs in on NoSQL’s choice to abandon Consistency (or to accept eventual consistency) in favour of Availability and Partition-Tolerance. Discarding a few improbable causes of database errors where CAP does not apply, Stonebraker argues that it is more likely that a single node will fail. Given that such a “partitioned” network can be overcome algorithmically, he recommends dropping partition-tolerance rather than consistency.