The document discusses the introduction of MongoDB 3.0, highlighting new features such as pluggable storage engines, enhanced concurrency through WiredTiger integration, and improved compression algorithms. It details advancements in querying tools, administration, and the replication limits, significantly increasing the capabilities and performance of the database system. Overall, MongoDB 3.0 aims to provide greater flexibility and efficiency for various operational needs.

2. Introduction to 3.0
By: Osmar “Oz” Olivo
Product Manager
MongoDB Inc.

3. Agenda
• Pluggable Storage Engines
• WiredTiger Integration
• Concurrency
• Compression
• Enhanced Querying & Tools
• Administration Enhancements
• Replication Enhancements

4. Pluggable Storage Engines

5. • Vision
– One data model, one API, one set of operational
concerns
» Under the hood, many options for every use
case under the sun
Storage Engine Layer

6. Storage Engine Layer
Content
Repo
IoT Sensor
Backend
Ad Service
Customer
Analytics
Archive
MongoDB Query Language (MQL) + Native Drivers
MongoDB Document Data Model
MMAP V1 WT In-Memory ? ?
Supported in MongoDB 3.0 Future Possible Storage Engines
Management
Security
Experimental in
MongoDB 3.0

7. WiredTiger Integration

8. Why WT?
They’re Grrrreat!

9. Why WT?
• WT product and team acquired by MongoDB
– Authors former members of Berkeley DB team
– Standalone engine in use in production today
• WT addresses weaknesses of MMAPv1
– Compression
– Highly concurrent and enables full hardware utilization
– More tunable

10. Concurrency

11. MMAPv1 Concurrency Improvements
• Collection Level Concurrency
– One lock per collection
– Write operations to a collection block all other
operations on that collection
– Read operations to a collection block writes to that
collection
• Allow other read operations to occur concurrently

12. Concurrency in WiredTiger
• Document Level Concurrency
– Uses various algorithms to minimize contention
between threads
– One thread yields on contention to same document
• Writes no longer block all other writes
• CPU utilization directly correlates with performance

13. Compression

14. Compression (WT only)
• Compression is on in WT by default
• 3.0 supports two compression algorithms
– snappy (default)
• Good compression benefits with little
CPU/performance impact
– zlib
• Extremely good compression at a cost of additional
CPU/degraded performance

15. Enhanced Querying & Tools

16. Indexing & Querying
• Explain() 2.0
– explain() revamped
• Now allows for improved query inspection
• Geospatial Big Polygon support
– Improved handling of polygons with an area greater
than a single hemisphere
• $dateToString operator in aggregation
– Allows user to specify string format for which to
convert a date into

17. Tools Improvements
• MongoDB Server Tools Rewritten in GO
– Removed all server dependencies
– Allows for much faster iteration
• Parallelized data loading tools
– dump/restore & import/export
– highly improved loading and export times

18. Administration Enhancements

19. Administration
• Role Based Auditing
– Auditing rules can be set to filter on specific roles
– Useful for auditing certain kinds of accesses or users
• Logging Improvements
– New component system
– Able to filter by severity levels

20. Replication

21. Replication
• Replica set limit raised from 12 to 50
• Meets a much higher HA standard
– Can deploy across many more regions and DC’s
– Increases locality of data across deployments
– Easier to guarantee local reads across many regions

23. Questions?