Learn about the ApsaraDB for MongoDB lifecycle policy, including how each stage affects purchasing, support, and maintenance. Plan version upgrades for ApsaraDB for MongoDB to avoid service disruptions.
Background
As the MongoDB open-source community evolves, MongoDB releases new versions with improved performance, security, and functionality. Meanwhile, the MongoDB open-source community discontinues support for older versions of MongoDB. Running an older version of MongoDB exposes you to security and stability risks. Upgrade to the latest version of MongoDB as soon as possible. We continuously enhance the reliability and performance of ApsaraDB for MongoDB.
Lifecycle stages and limitations
Each lifecycle stage has different limitations on purchasing, usage, and support.
|
Lifecycle stage |
Lifecycle limitations |
Continued service and support |
Recommendations |
|
General Availability (GA) |
None |
|
None |
|
End of Marketing (EOM) |
After the EOM date:
|
After the EOM date:
|
Upgrade to a later version of ApsaraDB for MongoDB as soon as possible. Upgrade the major version of an ApsaraDB for MongoDB instance. |
|
End of Full Support (EOFS) |
After the EOFS date:
|
After the EOFS date:
|
ApsaraDB for MongoDB no longer accepts support requests for this version and provides migration guidance instead. Upgrade as soon as possible. Upgrade the major version of an ApsaraDB for MongoDB instance. |
|
End of Service (EOS) |
After the EOS date:
|
None |
To avoid service disruptions, upgrade before your current version reaches EOS. Upgrade the major version of an ApsaraDB for MongoDB instance. |
ApsaraDB for MongoDB lifecycle stages
The following table shows the lifecycle schedule for each major version of ApsaraDB for MongoDB. Plan upgrades based on the schedule below.
Stage timelines may change based on product planning but will not be advanced.
|
Version |
Lifecycle stage |
EOM date |
EOFS date |
EOS date |
Recommended upgrade |
|
MongoDB 3.0 |
End of Service (EOS) |
New purchases were discontinued on November 22, 2019. |
July 31, 2024 |
December 31, 2024 |
MongoDB 8.0 or later |
|
MongoDB 3.2 |
End of Service (EOS) |
New purchases were discontinued on November 22, 2019. |
July 31, 2024 |
December 31, 2024 |
MongoDB 8.0 or later |
|
MongoDB 3.4 |
End of Marketing (EOM) |
New purchases were discontinued on January 1, 2023. |
June 30, 2026 |
December 31, 2026 |
MongoDB 8.0 or later |
|
MongoDB 4.0 |
General Availability (GA) |
New purchases of standalone instances stop on December 31, 2025. |
No plan yet |
MongoDB 8.0 or later |
|
|
MongoDB 4.2 |
General Availability (GA) |
No plan yet |
|||
|
MongoDB 4.4 |
General Availability (GA) |
||||
|
MongoDB 5.0 |
General Availability (GA) |
||||
|
MongoDB 6.0 |
General Availability (GA) |
||||
|
MongoDB 7.0 |
General Availability (GA) |
||||
|
MongoDB 8.0 |
General Availability (GA) |
||||
Service commitments and recommendations
-
before a key lifecycle milestone, Alibaba Cloud notifies your account contacts through announcements, messages, email, or SMS.
-
Compatibility
-
ApsaraDB for MongoDB does not guarantee compatibility between major versions. We strive to maintain syntax, interface, and feature compatibility, but potential incompatibilities are documented in Major version upgrade notes for ApsaraDB for MongoDB.
-
ApsaraDB for MongoDB guarantees minor version compatibility within the same major version, including syntax, interfaces, and features. Upgrade to the latest minor version for the newest fixes. Upgrade the minor version of an ApsaraDB for MongoDB instance.
-
-
Bug fixes
-
Upgrade to the latest major or minor version to apply bug fixes.
-