Today MongoDB 3.2 is generally available; you can download now.
Our community is critical to ensuring the quality of our releases. Thank you to everyone who participated in our 3.2 Bug Hunt. Winners were selected based on the user impact and severity of the bugs found.
Stuart Hall | SERVER-21690
Nick Judson | SERVER-21434
To learn more about MongoDB 3.2:
Announcing the General Availability of MongoDB 3.2 and Bug Hunt Winners
MongoDB 3.2 is now generally available for production deployments - you can download the community version or MongoDB Enterprise Server today. This is truly a giant release. MongoDB 3.2 features better support for robust, highly available multi-data center deployments, document validation to ensure you can leverage our flexible data model without sacrificing governance controls for data quality, improved tools for analytics, and much more. Click to tweet : .@MongoDB 3.2 is now generally available spr.ly/6006BrNvn Let’s take a look at what’s inside. New Storage Engines for New Use Cases We’re introducing new storage engines that extend the capabilities of MongoDB, including an in-memory storage engine for the most demanding real-time apps (currently in beta) and an encrypted storage to secure data at rest. Document Validation In MongoDB 3.2, you can now get the benefits of a flexible data model without sacrificing governance. With document validation , you can define rules on what's being stored in your database. MongoDB Compass MongoDB 3.2 introduces MongoDB Compass , a new tool that allows developers and DBAs to visualize and explore their MongoDB data without having to use the MongoDB query language. It’s a sophisticated and simple to use GUI. BI Connector The new BI Connector in 3.2 enables analysts, data scientists, and business users to visualize MongoDB data with industry-standard SQL-based BI platforms such as Tableau, Qlikview, and more. And so much more We’re only scratching the surface with the above. MongoDB 3.2 also introduces $lookup to join data across collections, enhancements to Cloud Manager and Ops Manager , partial indexes, and so much more. Learn more in our about MongoDB 3.2 page . Community Contribution & Bug Hunt Winners As always, we couldn’t have done it without the ongoing contribution and feedback from our community. Thank you to everyone who participated in the Bug Hunt and provided us with feedback on the new functionality. We’ve selected this year’s winner and honorable mention: Winner - Stuart Hall Stuart found SERVER-21690 , a 100x performance regression in text search with phrase matching with text index v3. After the bug was identified and fixed he helped us test the fix. Stuart has also reported other issues that are being investigated. Honorable Mention - Nick Judson Nick submitted SERVER-21434 , uncovering a bug in findAndModify returning unexpected results when there are multiple readers. The first prize winner and honorable mention received a $1500 and $500 Amazon gift card respectively, a free ticket to MongoDB World 2016, and a reserved front row seat at the conference. Congratulations to the winners and thanks to everyone who downloaded, tested and gave feedback on our release candidates. Learn More There are many ways to learn more about the newest version of MongoDB. Review our about MongoDB 3.2 page Read the What’s New in MongoDB 3.2 white paper Learn about 3.2 left outer joins and other aggregation enhancements in our 3 part blog series Watch the What’s New in MongoDB 3.2 on-demand webinar Review the 3.2 release notes Register for our presentation on Best Practices for Upgrading to MongoDB 3.2 The best way is to download and try it out. We’re excited for you to download MongoDB 3.2, click below: Download Community Download Enterprise
Considering NoSQL? Let's Break Down Your Options
Non-relational alternatives to relational databases — usually referred to as NoSQL databases — have been rapidly gaining popularity over the past decade. In 2013, MongoDB published one of our most popular white papers, “Top 5 Considerations When Evaluating NoSQL Databases.” We have since updated that paper as the technology has evolved. MongoDB is now offering a major update, which adds two new issues organizations should include in their thinking: how a database handles data generated at the edge by mobile devices and how a database fits into a broader data platform that includes search and analytics. If you’re testing the waters of NoSQL databases, then you’re probably familiar with how they’re different from traditional relational databases. The list of things you already know about NoSQL probably looks something like this: They use a different data model and query language. They have dynamic schemas. They scale horizontally. Beyond those common features, there are significant differences among NoSQL databases. The seven areas of significant differences among your options are: Data model (document, graph, key-value, etc.) Query model Consistency and transactional model APIs Mobile data Data platform Commercial support, community strength, and lock-in From MongoDB’s point of view, the most important consideration is the data model. We popularized the document model , which supports a superset of all data models, making it useful for a wide variety of applications. Key features include the ability to index and query in any field, and the natural mapping of document data structures to objects in modern programming languages. Recent shifts in how modern applications are developed and deployed — and in the experiences they offer customers — highlight the two new considerations. Mobile use cases: Mobile applications introduce the added challenge of not always being connected to the network. Developers need a solution for keeping all their customers’ apps in sync with the back-end database, no matter where they are in the world and what kind of network connection they have. The solution also needs to scale easily and quickly as more users download an app, and support the cutting edge of mobile development technologies as they evolve. Data platform: MongoDB’s application data platform provides developers a unified interface to serve transactional and operational applications alongside search, real-time, and data lake application needs. It eliminates the overhead and friction of developers having to stitch together multiple discrete technologies into a complex architecture, each creating its own duplicated data silo — connected by fragile ETL pipelines — and accessed, secured, governed, and operationalized by different APIs and tools. For a deep dive into all the differences among NoSQL databases, download our white paper, “ Top 7 Considerations When Evaluating NoSQL Databases .”