Skip to main content

Version policy

The version policy of FPT MongoDB Enterprise is designed to ensure system stability, security, and long-term compatibility, while providing customers with the flexibility to upgrade based on their requirements. The service is built on MongoDB Enterprise and operated by FPT Cloud in accordance with enterprise-grade standards.

General principles​

FPT MongoDB Enterprise applies version management based on the following principles:

  • Multi-version support : FPT MongoDB Enterprise supports multiple versions of MongoDB Enterprise, allowing customers to select and deploy a version that aligns with their application requirements and existing system compatibility.
  • Stable versions : Only stable and production-ready versions are made available. Each version is thoroughly tested, validated for compatibility, and optimized before being released on the platform.
  • Security patching : Critical security patches are applied periodically or on an emergency basis to ensure data protection and system integrity, while minimizing impact on customer workloads.
  • Flexible upgrade : FPT MongoDB Enterprise supports in-place version upgrades on existing clusters with minimal downtime. High availability architectures (such as Replica Set or Sharded Cluster) are designed to further reduce service disruption during the upgrade process.

Version structure​

FPT MongoDB Enterprise follows the versioning convention established by Mongo Inc.. The version structure typically consists of three components: major, minor and patch (Example: 8.0.19).

ComponentDescription
MajorSignificant changes in architecture or features, which may not be backward compatible.
MinorFeature/release branch version.
PatchSmaller updates, bug fixes, or security patches that are backward compatible.

Users can view the exact version they are using for their database cluster directly on the Console Portal by checking the details of their database cluster.

Version lifecycle​

Each version is managed according to a clear lifecycle consisting of the following phases: Preview (Beta), General Availability (GA), Deprecated (Dep.), and End of Support (EoS). FPT Cloud will provide advance notice of the end-of-support schedule so that customers can proactively plan their upgrades.

StageDescription
1. Preview (Beta)The version is in the testing phase and not guaranteed with SLA. Features may change or be removed at any time. Users can try it for evaluation, testing, or non-production environments. It is not recommended for production use.
On Console Portal, Beta versions are displayed with the "Beta" tag.
2. General Availability (GA)The version is stable, production-ready, and officially supported with SLA.
3. Deprecated (Dep.)The version is no longer recommended for new deployments and is preparing to reach End of Support (EoS) soon. It still works for existing systems. This stage signals that support will end.
On Console Portal, deprecated versions are displayed with the “Deprecated” or “Dep.” tag.
4. End of Support (EoS)The version is no longer supported.
On Console Portal, Beta versions are displayed with the "EoS" tag.

Note : Users are advised to proactively upgrade before the current version reaches the Deprecated or EoS stage to ensure the system's security and stability.

Recommendations​

ScenarioRecommended Action
Database cluster is running a GA versionContinue normal usage.
Database cluster is running a Beta versionRegularly follow the update announcements, as the version may change or be removed without prior notice.
Database cluster is running a Deprecated versionAvoid creating new instances/clusters and plan to upgrade to a newer supported version, as end-of-support is approaching with the current version.
Database cluster is running a GA versionMonitor and plan for an upgrade to ensure continued support and stability.

Supported versions​

Major VersionMinor VersionFDE PreviewFDE GAFDE DeprecatedFDE End of Support
8.08.0.2004/2026------
Last updated on by Dang Tran