Jonathan Ellis in a post about MySQL 5.6 and how Oracle got the whole NoSQL wrong, considering NoSQL is, in this exact order, about scaling, continuous availability, flexibility, performance, and queryability:
The big news for MySQL 5.6 was the inclusion of “NoSQL” features in
the form of a memcached api for get and put operations.
In cases like this, it’s tough to tell whether Oracle got this so
wrong deliberately to sow confusion in the market, or because they
really think that’s what NoSQL is about.
I know Jonathan Ellis has always had very strong opinions about the technical superiority of Cassandra and Cassandra is indeed a very solid solution, but I’m always reluctant to calling a competitor stupid and using the myopic argument “if I’m good at X and suck at Y, then what everyone is looking for is only X”.
Original title and link: DataStax’s Reaction to MySQL 5.6: Oracle’s MySQL Misses the NoSQL Mark ( ©myNoSQL)