What he lists as his transaction use case (update if unmodified) I do right now with Cassandra and an IF clause and a timestamp...
i.e. update foo set x = y AND last_modified_timestamp = 456789 IF last_modified_timestamp = 12345
see http://www.datastax.com/dev/blog/lightweight-transactions-in...
Cassandra was mature by late 2011 and we were using it in production back then (billions of records).
In any case, I would have a knee jerk reaction to not trust any database system that hit 1.0 a month before I wanted to start using it, especially for mission critical core data.
>Support asking for N number of Pins in a board in a deterministic order (such as reverse creation time or user specified ordering). Same for Pinner to likes, Pinner to Pins, etc.
This can be a pain to model in Cassandra. It would require denormalizing for every key you wanted to order on, and it generally makes updating data a pain.
With Cassandra, you can set replication factors, speed up the writes, and automatically shard the data without having to manage your own "mapping tables".