Downloaded 13 times
Uploaded bySveta Smirnova
MongoDB Engines: Demystified
The document explains the evolution and characteristics of storage engines in MongoDB, highlighting the transition from the original mmap engine to alternative engines like WiredTiger and MongoRocks. It details the performance benefits, features such as document-level locking and ACID compliance, and deployment configurations in different environments. Additionally, it mentions options for encryption and the flexibility offered by multiple engines within MongoDB architecture.
More Related Content
Similar to MongoDB Engines: Demystified
![Introduction into MySQL Query Tuning for Dev[Op]s](https://cdn.slidesharecdn.com/ss_thumbnails/qtdevops-210717011329-thumbnail.jpg?width=640&height=640&fit=bounds)
![Introduction to MySQL Query Tuning for Dev[Op]s](https://cdn.slidesharecdn.com/ss_thumbnails/qtdevops-191005204425-thumbnail.jpg?width=640&height=640&fit=bounds)
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
![谷歌留痕技术教程[ 𝙩𝙤𝙥 𝟮𝟯𝟯. 𝙘 𝙤𝙢 ]](https://cdn.slidesharecdn.com/ss_thumbnails/top233-260130173900-2eb784f9-thumbnail.jpg?width=640&height=640&fit=bounds)
MongoDB Engines: Demystified
- 1. MongoDB Engines Demystified April, 26,2017 Sveta Smirnova
- 2. • MySQL Supportengineer • Author of • MySQL Troubleshooting • JSON UDF functions • FILTER clause for MySQL • Speaker • Percona Live, OOW, Fosdem, DevConf, HighLoad... Sveta Smirnova 2
- 3. • First versionhad only one engine: MMAP History 3
- 4. • First versionhad only one engine: MMAP • MMAP was not ideal for all workloads • Collection-level locking • No ACID • No MVCC • Performance limited History 3
- 5. • First versionhad only one engine: MMAP • MMAP was not ideal for all workloads • TokuMX • Drop-in replacement • Document-level locking • ACID • MVCC • Scalability History 3
- 6. • First versionhad only one engine: MMAP • MMAP was not ideal for all workloads • TokuMX • Percona • Acquired Tokutek in 2015 • Percona Server for MongoDB History 3
- 7. • Not everyonewas happy with MMAP Why Other Engines? 4
- 8. • Not everyonewas happy with MMAP • Other solutions on market • TokuMX • WiredTiger • RocksDB Why Other Engines? 4
- 9. • Not everyonewas happy with MMAP • Other solutions on market • Version 3.0 • MongoDB acquires WiredTiger in 2014 • New Storage Engine API • WiredTiger is MongoDB storage engine Why Other Engines? 4
- 10. • Not everyonewas happy with MMAP • Other solutions on market • Version 3.0 • Percona Server for MongoDB • Released TokuMX as PerconaFT engine • Later discontinued Limitations of SE API • Added MongoRocks • Added Memory Why Other Engines? 4
- 11. • Only oneper mongod instance Engines in MongoDB 5
- 12. • Only oneper mongod instance • Many in multiple-instance setup • Replica Set • Sharding Engines in MongoDB 5
- 13. Memory WiredTiger Memory Multiple Engines inReplica Set 6
- 14. MongoRocks WiredTiger MongoRocks Multiple Engines inReplica Set 7
- 15. Shard 1 Shard2 MR MR MR WT WT WT Multiple Engines In Sharded Cluster 8
- 16. • Default since3.2 WiredTiger 9
- 17. • Default since3.2 • Document-level locking WiredTiger 9
- 18. • Default since3.2 • Document-level locking • MVCC/ACID WiredTiger 9
- 19. • Default since3.2 • Document-level locking • MVCC/ACID • Own Journal WiredTiger 9
- 20. • Default since3.2 • Document-level locking • MVCC/ACID • Own Journal • Compression WiredTiger 9
- 21. • Default since3.2 • Document-level locking • MVCC/ACID • Own Journal • Compression • Own memory management WiredTiger 9
- 22. • Default since3.2 • Document-level locking • MVCC/ACID • Own Journal • Compression • Own memory management • Online binary backups in Percona Server WiredTiger 9
- 23. • Default since3.2 • Document-level locking • MVCC/ACID • Own Journal • Compression • Own memory management • Online binary backups in Percona Server • Suites for any workload WiredTiger 9
- 24.
- 25. • 3.2+ • MongoDBEnterprise only Encrypted 10
- 26. • 3.2+ • MongoDBEnterprise only • Encryption at Rest Encrypted 10
- 27. • 3.2+ • MongoDBEnterprise only • Encryption at Rest • Based on WiredTiger Encrypted 10
- 28. • 3.2+ • MongoDBEnterprise only • Encryption at Rest • Based on WiredTiger • Percona suggests to use FS encryption Encrypted 10
- 29. • All datastored in memory In-Memory and Memory 11
- 30. • All datastored in memory • No persistence after restart In-Memory and Memory 11
- 31. • All datastored in memory • No persistence after restart • Can be combined with persistent storage In-Memory and Memory 11
- 32. • All datastored in memory • No persistence after restart • Can be combined with persistent storage • Based on WiredTiger In-Memory and Memory 11
- 33. • All datastored in memory • No persistence after restart • Can be combined with persistent storage • Based on WiredTiger • In-Memory • 3.2.6+ • MongoDB Enterprise only In-Memory and Memory 11
- 34. • All datastored in memory • No persistence after restart • Can be combined with persistent storage • Based on WiredTiger • In-Memory • Memory • 3.2.8-2.0+ • Percona Server for MongoDB • Open Source In-Memory and Memory 11
- 35.
- 36. • 3.0+ • PerconaServer for MongoDB MongoRocks 12
- 37. • 3.0+ • PerconaServer for MongoDB • Compaction MongoRocks 12
- 38. • 3.0+ • PerconaServer for MongoDB • Compaction • Compression MongoRocks 12
- 39. • 3.0+ • PerconaServer for MongoDB • Compaction • Compression • Online binary backups MongoRocks 12
- 40. • 3.0+ • PerconaServer for MongoDB • Compaction • Compression • Online binary backups • MVCC/ACID MongoRocks 12
- 41. • 3.0+ • PerconaServer for MongoDB • Compaction • Compression • Online binary backups • MVCC/ACID • Best suited for • Large data • Write-intensive workloads MongoRocks 12
- 42. • Based onoriginal MMAP MMAPv1 13
- 43. • Based onoriginal MMAP • Default < 3.2 MMAPv1 13
- 44. • Based onoriginal MMAP • Default < 3.2 • Memory-mapped files MMAPv1 13
- 45. • Based onoriginal MMAP • Default < 3.2 • Memory-mapped files • Collection-level locking MMAPv1 13
- 46. • Based onoriginal MMAP • Default < 3.2 • Memory-mapped files • Collection-level locking • Memory management delegated to system MMAPv1 13
- 47. • Based onoriginal MMAP • Default < 3.2 • Memory-mapped files • Collection-level locking • Memory management delegated to system • No compression MMAPv1 13
- 48. • Based onoriginal MMAP • Default < 3.2 • Memory-mapped files • Collection-level locking • Memory management delegated to system • No compression • No MVCC/ACID MMAPv1 13
- 49.
- 50.
- 51.
- 52. • Storage enginesprovide great flexibility • They can be used in combinations • MongoDB architecture allows easily to test if engine suits your needs • Percona Server for MongoDB • 100 % Open Source • Includes Enterprise-grade features • Has reach monitoring Summary 15
- 53. • MMAPv1 • WiredTiger •MongoRocks • Percona Memory Engine • PMM Demo More informaiton 16
- 54.
- 55.