MongoDB 2.6 Released

A lot of hype... And we still have db level locking. If document level is too difficult, at LEAST do collection level (not that it is too much better, but least it some real improvement).

And it <i>still</i> relies entirely on the OS&#x27;s scheduling algorithms for caching and IO. mmap is nice but it has no idea you&#x27;re running a database.

Here are the release notes. <a href="http://docs.mongodb.org/master/release-notes/2.6/" rel="nofollow">http:&#x2F;&#x2F;docs.mongodb.org&#x2F;master&#x2F;release-notes&#x2F;2.6&#x2F;</a>

<i>Finally, MongoDB 2.6 lays the foundation for massive improvements to concurrency in MongoDB 2.8, including document-level locking.</i><p>This is exciting even if I don&#x27;t expect it to happen soon.

With this release aggregation framework got super powerful. Now it returns a cursor. Now we can get the aggregation results and iterate over them. No more 16mb result limitation as well...

I&#x27;ve been using Elasticsearch as a primary database for my new project, which has basically been a good NoSQL db that happens to have great search. However, peripheral tools(performance testing, hosting) have been a bit rough.<p>How do the two databases compare now. Is search improving in Mongo or is that something they are not really worrying about at the moment.

This is good write-up about what&#x27;s new with actual numbers. <a href="http://devops.com/news/mongodb-2-6-significant-release-mongo-yet/" rel="nofollow">http:&#x2F;&#x2F;devops.com&#x2F;news&#x2F;mongodb-2-6-significant-release-mongo...</a> Quote: &quot;MongoDB 2.6 provides more efficient use of network resources; oplog processing is 75% faster; classes of scan, sort, $in and $all performance are significantly improved; and bulk operators for writes improve updates by as much as 5x.&quot;

Awesome news. I am excited for the aggregation cursor. As much as I love some of the alternatives that are almost ready I still turn to mongo for a vast majority of my deployments. Hopefully it will keep getting better and pushing others to do the same.

Can someone with more MongoDB experience give me your thoughts on the upgrade difficulty here? Worth doing soon, or waiting for a point release? Does this require a data rebuild&#x2F;update process (coming from 2.4)?

So i&#x27;ve been trying to find an the ideal case for mongodb, because I have to teach a nosql database to some people I am mentoring.<p>I&#x27;m leaning heavily towards couchdb though.<p><a href="http://daemon.co.za/2014/04/when-is-mongodb-the-right-tool" rel="nofollow">http:&#x2F;&#x2F;daemon.co.za&#x2F;2014&#x2F;04&#x2F;when-is-mongodb-the-right-tool</a>

Some notes on using the shell, and some unforeseen performance changes from the beta: <a href="http://comerford.cc/wordpress/2014/03/28/mongodb-2-6-shell-performance/" rel="nofollow">http:&#x2F;&#x2F;comerford.cc&#x2F;wordpress&#x2F;2014&#x2F;03&#x2F;28&#x2F;mongodb-2-6-shell-p...</a>

Cursor for aggregate, proper explain for aggregate, index intersection, $redact and other cool operators, Multi* in Geospatial, faster execution and, foundation for document-level locking which should be introduced in MongoDB 2.8. I must say I&#x27;m happy with this release.

Playing with Meteor and mongo recently and have found mongo seems a little bit strange from a transitional SQL point of view, like do I need to embed or reference? Can anyone recommend a good book or source?

So does this mean document level locking has been implemented or just the foundation for its future implementation has been laid?<p>I can&#x27;t hold my breath much longer! :-)<p>Edit: docs don&#x27;t make any mention of it but then again they probably haven&#x27;t updated them yet (fingers crossed!) <a href="http://docs.mongodb.org/manual/faq/concurrency/#what-type-of-locking-does-mongodb-use" rel="nofollow">http:&#x2F;&#x2F;docs.mongodb.org&#x2F;manual&#x2F;faq&#x2F;concurrency&#x2F;#what-type-of...</a>

I am a big fan of their focus on manageability for sharded databases. I am less of a fan of their db internals that might require you to use many more shards than a more performant engine. More details at <a href="http://smalldatum.blogspot.com" rel="nofollow">http:&#x2F;&#x2F;smalldatum.blogspot.com</a>

The blog post was rather vague about 2.6&#x27;s &quot;better performance&quot;. Are there any concrete numbers?

The main reason I use MongoDB on Node is the maturity of the Mongoose ORM - I&#x27;ve used Node-ORM 2, BookshelfJS, and SequelizeJS and none of them felt as mature as Mongoose.

How is it possible to have aggregation cursors without crunching the complete data set in advance (aka map&#x2F;reduce) and still have consistent and correct results?

Will MongoDB still segfault under certain circumstances?

I wonder, what does this mean for TokuMX

Mongo haven&#x27;t updated their feeds for Ubuntu. I wonder how long they will take to do so?

mongodb is the best database in the whole wide world at the moment. I encourage everyone to jump in mongodb for agile web scale development with full big data capability.

I have never understood how the definition of &quot;Document Database&quot; is different from &quot;File System&quot;.