The serious part of Oracle NoSQL is a practical approximation of ACID compliance, the standard that SQL databases like to offer.
If this claim holds up, then its easy to see where Oracle could come out ahead of other NoSQL databases. TFA mentions that this practical approximation is dealt with by arranging the cluster machines in two axes: the replication axis and the sharding axis. Along the sharding axis, each major key is guaranteed to be tied to a single machine. Since there is only one record to be updated, there is no "eventual consistency" problem. The replication axis is responsible for making multiple copies of that data. If full ACID compliance is desired, even along the replication axis, there are plenty of options for ensuring that the write is complete before calling the transaction complete: the master node is updated, a majority of replicated nodes are updated, or all replicated nodes are updated.
This approach seems to take the best of both worlds in the NoSQL arena: sharding, which is the approach used by MySQL cluster, and replication, as used by pretty much every other NoSQL store available. Of course, if you have a fuck-ton of data, you'll also need a fuck-ton of machines. This is not a server you will be testing without considerable resources at your disposal.