Xaprb

Stay curious!

Bold predictions on which NoSQL databases will survive

with 7 comments

In case you’ve been living under a rock for the last 5 years, the NoSQL movement has changed. There was a time when everyone — EVERYONE — was dumping on relational databases, and MySQL in particular. Nonsense like “SQL itself is inherently unscalable” routinely came out of the mouths of otherwise usually sensible people. But that’s cooled off a little bit, thank heavens.

And what’s the new hotness? Well, Big Data, of course! But I digress. In the world of databases, it’s move over NoSQL, heeeeeere’s NewSQL. I’m talkin’ NuoDB, Clustrix, MySQL Cluster (NDB), and so forth. A lot of people now recognize that it wasn’t SQL or the relational model that was a problem — it was the implementations that had some issues. The pendulum has swung a little away from vilifying SQL, and we don’t talk about NoSQL as much as we talk about document-oriented or key-value or whatever.

Does that spell death for NoSQL databases? Not in my opinion. But I am just in the mood to stick my neck out a bit today, so I’m going to do something I don’t normally do — predict the future. Here’s my prediction: there may be many NoSQL databases that live long and healthy lives, but among them will probably be MongoDB, Redis, and Riak.

Discuss!

PS: this prediction is about what I think will happen. If I get one out of three right, I’ll be happy. It’s not an endorsement of any database, dismissal of any other database, or an opinion about what I think should happen. Limitations and exclusions apply. Subject to credit approval, see store for details.

Written by Xaprb

January 10th, 2013 at 10:20 pm

Posted in SQL

7 Responses to 'Bold predictions on which NoSQL databases will survive'

Subscribe to comments with RSS

  1. Why isn’t OrientDB on this list?

    EllisGL

    10 Jan 13 at 10:31 pm

  2. The only survivor I’d guess be the one which are ready to be flexible…. Defining the purpose of using NoSQL and efficiently relating it with YesSQL is the way to go (at least for few more years) for scalability. We use Redis for search in top of our MySQL database, I doubt if MySQL would give such efficiency, specially when it comes to extensive search. I don’t predict anyone to die, but I have psychik feeling that MyISAM may come good someday :D :D

    Rajib

    11 Jan 13 at 5:14 am

  3. memcached. People forget it’s a NoSQL database, because it was a key-value store long before people were talking about it. I think Hadoop will survive, it has a lot of power in the analytics world.

    And I agree with Redis and Riak, I’m not sure about MongoDB (even though I want it to thrive, as I personally know many of the employees and the founder).

    Sheeri K. Cabral

    11 Jan 13 at 11:37 am

  4. I agree with Sheeri, except about MongoDB. I think Mongo will survive because 10gen. I think you need to include a graph database in there as well: Neo4j or OrientDB. I don’t think Apache Cassandra or CouchDB are going to go away so soon.

    With NoSQL being such a broad term, it is hard to predict the size and scope of it in the coming years.

    Joshua Dickerson

    11 Jan 13 at 6:12 pm

  5. That is a pretty good list. Redis is backed up by the porn industry:
    http://highscalability.com/blog/2012/4/2/youporn-targeting-200-million-views-a-day-and-beyond.html

    MongoDB is still picking up steam and starting to show signs of maturity in that its shortcomings are becoming more well known.

    Eric Bergen

    11 Jan 13 at 6:14 pm

  6. I wouldn’t be surprised to see at least one of the apache foundation’s noSQL solutions to survive. In the noSQL lifecycle, HBASE has been around for eternity, although that may be one reason it doesn’t survive. Both CouchDB and Cassandra seem specialized enough to keep them afloat for the long haul though.

    Gregory Haase

    11 Jan 13 at 8:02 pm

  7. Why isn’t OrientDB on the list? 1) please re-read the post and 2) please see http://www.google.com/trends/explore#q=mongodb%2C%20orientdb&cmpt=q

    Xaprb

    12 Jan 13 at 10:14 am

Leave a Reply