April 17, 2014

MongoDB is growing up

I caught up with my clients at MongoDB to discuss the recent MongoDB 2.6, along with some new statements of direction. The biggest takeaway is that the MongoDB product, along with the associated MMS (MongoDB Management Service), is growing up. Aspects include:

Of course, when a DBMS vendor rewrites its code, that’s a multi-year process. (I think of it at Oracle as spanning 6 years and 2 main-number releases.) With that caveat, the MongoDB rewrite story is something like:

Also, you can now straightforwardly transform data in a MongoDB database and write it into new datasets, something that evidently wasn’t easy to do before.

One thing that MongoDB is not doing is offer any ODBC/JDBC or other SQL interfaces. Rather, there’s some other API — I don’t know the details — whereby business intelligence tools or other systems can extract views, and a few BI vendors evidently are doing just that. In particular, MicroStrategy and QlikView were named, as well as a couple of open source usual-suspects.

As of 2.6, MongoDB seems to have a basic integrated text search capability — which however does not rise to the search functionality level that was in Oracle 7.3.2. In particular:

And finally, some business and pricing notes:

And finally, MongoDB did something many companies should, which is aggregate user success stories for which they may not be allowed to publish full details. Tidbits include:

  • Over 100 organizations run clusters with more than 100 nodes. Some clusters exceed 1,000 nodes.
  • Many clusters deliver hundreds of thousands of operations per second (combined read and write).
  • MongoDB clusters routinely store hundreds of terabytes, and some store multiple petabytes of data. Over 150 clusters exceed 1 billion documents in size. Many manage more than 100 billion documents.


16 Responses to “MongoDB is growing up”

  1. Mathieu Longtin on April 17th, 2014 11:53 am

    Anything on their relationship with TokuMX?

  2. norbert on April 17th, 2014 3:23 pm

    pitty they didn’t think about a Caching mechanism

  3. Curt Monash on April 17th, 2014 4:52 pm

    Last I heard, MongoDB (the company) wasn’t friendly to TokuMX (the product). I think that was late last year, but I’m not aware of anything changing.

  4. Ben Stephen on April 21st, 2014 3:07 am

    What is mongodb.. anyother relationship between database management system.. please let me know?

  5. Curt Monash on April 21st, 2014 12:03 pm

    MongoDB is by most measures the most successful NoSQL data manager, with a data model based on the JSON data interchange standard. It’s open source, but developed primarily by one company, which recently changed its name from 10gen to MongoDB.

  6. MongoDB 2.6: la nueva versión | BigData4Success on April 23rd, 2014 8:00 am

    […] DBMS2: MongoDB is growing up […]

  7. Joe Travaglini on April 23rd, 2014 4:03 pm

    Not to belabor the point, but which security buzzwords have you checked off?

    I have read about the new Mongo “field-level redaction”, and the implementation is interesting, to say the least:


    It’s a step in the right direction, for sure. But I would also say that it’s far from filling in the box on an Enterprise security checklist.

  8. Curt Monash on April 23rd, 2014 9:41 pm

    I don’t work for MongoDB, except as an analyst/consultant, so I haven’t personally checked off much of anything. And perhaps I nodded my head a bit too quickly at seeing mention of FIPS.

    But they’ve certainly take some substantive security steps.

  9. Tim on April 24th, 2014 5:11 am

    Still can’t believe these guys keep shipping the default install listening on *all* network interfaces. I major security flaw imho. 🙁

  10. Devarajaswami on April 25th, 2014 2:16 pm

    What about the dreaded global write lock?
    Is it still there or finally gone?

  11. Curt Monash on April 25th, 2014 7:30 pm

    See the first point in my post under “A reasonable locking strategy” 🙂

  12. Kelly Stirman on May 1st, 2014 8:42 am

    @norbert – mongodb reads and writes data to memory-mapped files. many deployments use mongodb for persistence and cache.

    @joe – here’s a new paper that covers features, integrations and best practices related to security: http://info.mongodb.com/rs/mongodb/images/MongoDB_Security_Architecture_WP.pdf

    @tim – official .deb and .rpm packages have the bind_ip configuration set to by default. more here: http://docs.mongodb.org/manual/administration/configuration/#configure-the-database

  13. Notes and comments, May 6, 2014 | DBMS 2 : DataBase Management System Services on May 6th, 2014 9:47 am

    […] I talked about when I visited MongoDB is confidential; the public stuff was mainly in my recent MongoDB technology post. But in one exception, I asked Max for an update as to MongoDB enterprise use cases. He reported a […]

  14. Where the innovation is | DBMS 2 : DataBase Management System Services on January 19th, 2015 3:29 am

    […] and Variability have been solved. MongoDB, Cassandra and perhaps others are strong NoSQL choices. Schema-on-need is in earlier days, but may […]

  15. MongoDB 3.0 | DBMS 2 : DataBase Management System Services on February 12th, 2015 6:26 pm

    […] No change in read performance (which however was boosted in MongoDB 2.6). […]

  16. MongoDB 3.4 and “multimodel” query | DBMS 2 : DataBase Management System Services on November 23rd, 2016 7:01 am

    […] neglected to ask why this changed from MongoDB’s adamantly non-SQL approach of 2 1/2 years […]

Leave a Reply

Feed: DBMS (database management system), DW (data warehousing), BI (business intelligence), and analytics technology Subscribe to the Monash Research feed via RSS or email:


Search our blogs and white papers

Monash Research blogs

User consulting

Building a short list? Refining your strategic plan? We can help.

Vendor advisory

We tell vendors what's happening -- and, more important, what they should do about it.

Monash Research highlights

Learn about white papers, webcasts, and blog highlights, by RSS or email.