What’s new in MongoDB 3.2

MongoDB 3.2 includes document validation enhancements, an encrypted storage engine, the new MongoDB Connector for BI, improvements to Ops Manager and Cloud Manager, and the introduction of a graphical interface to MongoDB called Compass. Key features include WiredTiger as the default storage engine, replication election enhancements, config servers as replica sets, readConcern, and document validations.

New Default MongoDB Storage Engine: WiredTiger

MongoDB 3.2 now uses WiredTiger as its default storage engine. When compared to the original MMAP storage engine used in earlier MongoDB releases, WiredTiger’s more granular concurrency control and native compression improve performance by 7-10x, while reducing storage overhead by up to 80%.  Starting in 3.2, MongoDB uses the WiredTiger as the default storage engine.

New MongoDB Encrypted Storage Engine

MongoDB supports a variety of encryption schema, with AES-256 (256 bit encryption) in CBC mode being the default. AES-256 in GCM mode is also supported. The encryption schema can be configured for FIPS 140-2 compliance.

MongoDB Compass: DBAs and development teams have come to rely on powerful graphical tools for their databases. MongoDB Compass empowers users to quickly and securely explore their databases, visually construct queries, inspect records and make smarter decisions about their deployments.

MongoDB Connector for BI: Business analysts, data scientists and executives can quickly explore and gain new insights from modern applications using the same BI tools they have installed on millions of devices to understand the data in their legacy systems.

Application Performance Monitoring Tool Integrations: With MongoDB 3.2, DBAs and operations teams are now able to operationalize MongoDB alongside their relational databases, preserving investments in skills and popular APM tools such as New Relic and AppDynamics.

Replication Election Enhancements

Starting in MongoDB 3.2, MongoDB reduces replica set failover time and accelerates the detection of multiple simultaneous primaries. As part of this enhancement, MongoDB introduces a version 1 of the replication protocol. New replica sets will, by default, use protocolVersion: 1. Previous versions of MongoDB use version 0 of the protocol. In addition, MongoDB introduces a new replica set configuration option electionTimeoutMillis.electionTimeoutMillis specifies the time limit in milliseconds for detecting when a replica set’s primary is unreachable.


Leave a Reply

Your email address will not be published. Required fields are marked *