I noticed in this article about Cassandra 1.2 that they have added the concept of vnodes, which allow you to have multiple nodes on a piece of hardware. This is pretty much the same as Oracle NoSQL Database's capability to place multiple Rep Nodes per Storage Node using the Capacity parameter.
It's official: we've shipped Oracle NoSQL Database R2.
Of course there's a press release, but if you want to cut to the chase, the major features this release brings are:
In an earlier post I noted that Berkeley DB Java Edition cleaner performance had improved significantly in release 5.x. From an Oracle NoSQL Database point of view, this is important because Berkeley DB Java Edition is the core storage engine for Oracle NoSQL Database.
Berkeley DB Java Edition 5.x has significant performance improvements. One user noted that they are seeing a 20x improvement in cleaner performance.
Here's an interesting article on YCSB benchmarks run on Cassandra, HBase, MongoDB, and Riak. Compare these to the Oracle NoSQL Database YCSB performance test results.
Here's an Oracle NoSQL Database customer success story for Passoker, an online betting house.
http://www.oracle.com/us/corporate/customers/customersearch/passoker-1-nosql-ss-1863507.html
There are a lot of great points made in the Solutions section, but as a developer the one I like the most is this one:
Here's an implementation of the Blueprints API for Oracle NoSQL Database.
https://github.com/dwmclary/blueprints-oracle-nosqldb
We ran a set of YCSB performance tests on Oracle NoSQL Database using SSD cards and Intel Xeon
E5-2690 CPUs with the goal of achieving 1M mixed ops/sec on a 95% read / 5% update workload. We used the standard YCSB parameters: 13 byte keys and 1KB data size (1,102 bytes after serialization). The maximum database size was 2 billion records, or approximately 2 TB of data.
We ran some benchmarks using FusionIO ioDrive2 SSD drives and Oracle NoSQL Database. FusionIO has published a whitepaper with the results of the benchmarks.