Chapter 1 of 8 · 3 practices · 2 min · 3-question quiz
Versions and deployment
Which MongoDB versions are supported, why every deployment should be a replica set, and how to approach a major upgrade.
Start: Run a supported MongoDB version and track end-of-life dates3 practices in this chapter
- 1Run a supported MongoDB version and track end-of-life datesEach MongoDB release has a published end-of-life date, after which it gets no fixes, including security fixes. If you are on 6.0 or older, you are already unsupported. 7.0 reaches end of life in…
- 2Deploy a replica set, even for small applicationsA standalone
mongodhas no automatic failover, so one crashed machine means downtime, and it cannot run multi-document transactions, which need a replica set (or a sharded cluster). - 3Read the release notes and known issues before a major upgradeMajor upgrades change defaults and occasionally ship with known issues. The 9.0 release notes, for example, list: A per-operation memory limit (see the queries chapter) that can make heavy…
Check yourself on this chapter
3 questions, right here once you are signed in. Your progress is saved as you read.