MongoDB Bootcamp
A two-week sprint to be production-ready with MongoDB.
Bootcamp plan
EXAMPLE
# MongoDB bootcamp - 10 working days Day 1 - Tooling: install, mongosh, Compass, VS Code playgrounds. Day 2 - Data modelling: embed vs reference, schema design rules. Day 3 - CRUD: find, insert, update, delete; upsert; bulk writes. Day 4 - Indexes: B-tree, compound, multikey, partial, TTL, text. Day 5 - Aggregation: \$match, \$group, \$lookup, \$facet, \$merge. Weekend project: a small marketplace with orders + items + payments. Day 6 - Transactions + sessions: when to use, retries, isolation. Day 7 - Performance: explain plans, hint, profiler, Atlas Performance Advisor. Day 8 - Replication + sharding: oplog tailing, replica set, shard keys. Day 9 - Security: auth, RBAC, network, CSFLE, audit. Day 10 - Backups + operations: mongodump, snapshots, PITR, drill restores. Capstone: ship a small API with Mongo on Atlas; include a backup drill. ## Tips - Embed for bounded lists; reference for unbounded or shared lookups - Compound index field order: equality first, then sort field - Use Atlas Performance Advisor on dev clusters; it learns from real traffic - Schema validation can prevent garbage docs; turn it on once schemas stabilise ## Common mistakes - Storing growing arrays (audit logs, events) inside a single doc - Misordered compound indexes that the optimiser cannot use - Running without backup verification - test restores quarterly
Why it matters
Mongo rewards modelling for your access patterns, not for SQL-shaped normalisation. The bootcamp pace lets you cover modelling + indexing + ops + backups in two weeks - more than enough to ship a real service.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…