There are a number of other systems that allow this same approach of consistency and high availability. For example, Cassandra, which is freely available (as required by the poster), appears to be able to give you this behavior if you set ConsistencyLevel to QUORUM.
Clustrix, the company I work for, offers a full SQL data store with similar quorum semantics. However, it's not free.
Google Megastore allows similar consistency semantics (with its own data model) in a cross data center "cloud" fashion. It's also not free, but it would probably be suitable for some set of Heroku customers, particularly if they're already using Google App Engine.
You actually cannot implement strongly consistent compare-and-set on a quorum based system. This is because quorums do not have strong failure semantics.
For example, lets say you have key A with data 'foo' living on all 3 nodes of a quorum based system. You perform a write to key A with data 'bar' and one host accepts the write and two fail resulting in your client getting a failure back. Reading data back from all nodes will return 'foo'. Time goes along and read repair or some other anti-entropy process kicks in a replicates 'bar' to the other hosts. Now a read for key A returns 'bar'. In short, when a client performs a write and gets a failure back they actually have no idea if it will update the data store or not. You cannot implement compare-and-set in that type of environment.
That is not how paxos works. It guarantees that all hosts in the system learn the same sequence of writes. The scenario where "one host accepts the write and two fail" does not happen. This is proved in http://research.microsoft.com/users/lamport/pubs/paxos-simpl...
Right, I was talking about the quorum semantics as used by systems like Dynamo and Cassandra. Paxos provides a much stronger guarantee than simple quorums.
Clustrix, the company I work for, offers a full SQL data store with similar quorum semantics. However, it's not free.
Google Megastore allows similar consistency semantics (with its own data model) in a cross data center "cloud" fashion. It's also not free, but it would probably be suitable for some set of Heroku customers, particularly if they're already using Google App Engine.