Announcing MongoDB Server 8.0 Platform Support Improvements

Alexandre Ettouati

Last month at MongoDB.local NYC 2024, we announced the preview of MDB 8.0, the next evolution of MongoDB’s modern database. With MongoDB 8.0, we’re focused on delivering the unparalleled performance, scalability, and operational resilience necessary to support the creation of next-generation applications.

For that to be possible, users must be able to deploy MongoDB on industry-standard operating systems. As a result, we are updating our Server Platform Policy to ensure that customers have the best possible experience when using MongoDB.

Starting in MongoDB 8.0, there will be two new changes:

  1. When a new major version of MongoDB is released, we will only release it operating system (OS) versions that are fully supported by the vendor for the duration of the MongoDB version’s life. In short, we will support an operating system if the operating system’s Extended Lifecycle Support (ELS) date is after the MongoDB Server’s End of Life (EOL) date.

  2. We will release new MongoDB Server versions (both major and minor) on the minimum supported minor version of the OS (defined by the OS vendor). Once an OS minor version is no longer supported by the vendor, we will update future MongoDB Server versions to the next supported OS minor version.

As always, MongoDB reserves the right to discontinue support for platforms based on lack of user demand and/or technical difficulties (e.g., if a platform doesn’t support required libraries or compiler features).

Ensuring best-in-class security

MongoDB routinely updates our documentation to indicate which platforms a new version of the MongoDB Server will be available on with the general availability release of that new server version.

To ensure that MongoDB customers can meet strong regulatory and security requirements, our software is developed, released, and distributed in accordance with industry security best practices. Given the mission-critical nature of MongoDB’s business—providing a highly secure, performant data platform to tens of thousands of customers in over 100 countries—we strive to provide strong and consistent security assurances across all of our products. In addition, MongoDB partners also need guarantees about the security development lifecycle of our products so they can provide the best experience to their customers.

By ensuring that our software runs only on platform versions that are receiving security patches, we aim to limit the vulnerabilities that might be introduced by customers running EOL operating systems.

The significance of this change

With every major server release, MongoDB determines the supported builds for that general availability (GA) release according to the planned vendor platform’s end of life date —meaning the MongoDB major release will not support the operating system if the operating system’s extended lifecycle support ends before the MongoDB EOL date. This also applies to server container images delivered to our customers.

Furthermore, to guarantee security assurances for operating systems that have a minimum minor version, we will only build new versions of MongoDB Server software on a vendor-supported major/minor version of the operating system. Concretely, we will build new versions of MongoDB on a minimum minor version until it hits a maintenance event (defined on a per-vendor basis), and at that point future MongoDB server builds will be updated to the new supported minor version.

Separately, when a vendor publishes a new major version of an operating system after a given version of MongoDB reaches GA, we will evaluate whether the latest MongoDB release will run on this new OS version, or we will wait for the next major MongoDB release before documenting formal platform support on our website.

Walkthrough: How it could work for you

Consider the RHEL 9 Planning Guide below and the hypothetical release cadence of MongoDB version X.0. As long as version X.0 is released three years before the end of RHEL 9 support, which as noted by RHEL is 2032, we will provide support on RHEL 9. This means that 2029 will be the last year that MongoDB releases a server version on RHEL 9.

Next, consider that version X.0 will be released at the end of 2025. Following the Extended Update Support Plan, we will build version X.0 on RHEL 9.6 until the start of 2026 when RHEL 9.8 becomes available. And then for future versions, MDB X.Y will begin being built on RHEL 9.8 until we require the minimum version to be 9.10 in 2027.

Diagram of the RHEL 9 planning guide. The left side of the chart features ratings from 9.0 up to 9.10. The bottom of the chart has the years from 2022 to 2032. The bars within the chart represent dark blue as minor release, light blue as extended update support, and light green as enhanced extended update support. The dark blue, minor release, starts in 2022 at 9.0 and reaches 9.10 in 2027. Light blue, extended update support, starts at the end of 2022 and peaks at 9.8 in 2026. Finally, the light green, enhanced extended update support, starts at 9.0 in 2024 and reaches 9.8 in 2028.
RHEL 9 planning guide

Building the future

Overall, these coming changes to the MongoDB Server Platform Policy underscore MongoDB’s commitment to helping developers innovate quickly and easily while providing an even more highly secure and performant data platform.

Stay tuned for additional updates about MongoDB 8.0—which will provide optimal performance by dramatically increasing query performance, improving resilience during periods of heavy load, making scalability easier and more cost-effective, and making time series collections faster and more efficient.

For more information about the Server Platform Policy updates, please refer to our documentation.