<story><title>MongoDB 2.0 Should Have Been 1.0</title><url>http://luigimontanez.com/2011/mongodb-2.0-should-have-been-1.0/</url></story><parent_chain></parent_chain><comment><author>rkalla</author><text>I don&apos;t intend this comment to be an insightful deconstruction of the NoSQL space and/or Mongo... but does anyone else notice that the level of energy around a project (positive or negative) &lt;i&gt;usually&lt;/i&gt; indicates its progress along the hype-dissolution cycle[1]?&lt;p&gt;I try not to take the actual comments or articles as law, but rather use them as a temperature reading to figure out where in the slope we are currently for a given tech or trend.&lt;p&gt;Given that Mongo-talk has absolutely dominated HN over the weekend as well as reddit/r/programming, I am interpreting this as being in the bottom of the dissolution curve right now.&lt;p&gt;It is this point where the community push-back and temporary &quot;hating on&quot; forces the team to go into overdrive, addressing whatever pain points the community has griped on the loudest, in this case:&lt;p&gt;&lt;pre&gt;&lt;code&gt;  - Write locks
  - Durability / Replication consistency (already addressed)
&lt;/code&gt;&lt;/pre&gt;
This is like tempering steel by pounding on it... but instead it is the community pounding on the people over at 10gen. That sucks, but this right of passage for them will see sweeter days on the other side.&lt;p&gt;I imagine Mongo 3.0 will represent the final climb out of the dissolution curve where all open complaints have been addressed and we actually get back to solving problems with the technology.&lt;p&gt;I don&apos;t know that Cassandra or Redis or CouchDB have completed their hype-cycles yet, because they haven&apos;t had the hyper-aggressive response from the community during the dissolution step. They are all popular and well-liked, but it seems like their popularity is still climbing.&lt;p&gt;It is all interesting none the less. Mongo is a huge success, regardless of how many of these articles are written.&lt;p&gt;I&apos;ve not seen a team as dedicated and involved like 10gen is for a long time; Eliot still answered 100s of messages on the group every week (Along with every new member of the team) -- which I find the biggest indicator of Mongo&apos;s future success. If the CTO is carving out that much time during the day to stay involved, while still bug fixing, replying to posts like these and testing bug reports... that&apos;s a lot of love right there.&lt;p&gt;[1] &lt;a href=&quot;http://en.wikipedia.org/wiki/Hype_cycle&quot; rel=&quot;nofollow&quot;&gt;http://en.wikipedia.org/wiki/Hype_cycle&lt;/a&gt;</text></comment>
<story><title>MongoDB 2.0 Should Have Been 1.0</title><url>http://luigimontanez.com/2011/mongodb-2.0-should-have-been-1.0/</url></story><parent_chain></parent_chain><comment><author>matthewcford</author><text>I&apos;ve been using MongoDB for well over a year now in around 6 apps (moved on from CouchDB) and I agree prior to 1.8 it should have been made more obvious that there were still some stability issues.&lt;p&gt;I have seen first hand some of the issues raised, we&apos;ve had data disappear, recurring random crashes, ect.  But I think the difference is &apos;everyone&apos; knew that there were issues with MongoDB, you just needed to check in jira. Jumping to 1.0 too early is clearly part of the reason for this backlash as not everyone thinks to check the issues because they&apos;ve come to believe 1.0 means its ready for mass adoption.&lt;p&gt;That being said, I love MongoDB and I would still use it in other apps, just got to decide if it&apos;s the right tool for the job.</text></comment>