Skip to main content

Overview

FPT MongoDB Enterprise is a fully managed NoSQL Database-as-a-Service built on the MongoDB Enterprise platform. You deploy, operate, and scale MongoDB clusters without managing the infrastructure underneath — no servers to patch, no replication to wire up by hand.

The service covers the operational work that usually sits between you and a working database: provisioning, automated backup and point-in-time recovery, real-time monitoring, alerting, elastic resource scaling, and centralized configuration. FPT Cloud's operations team runs it around the clock against an SLA.

What it runs​

MongoDB Enterprise, in two deployment architectures: Single Node and Replica Set. The same service therefore covers a developer sandbox and a production system with failover. Several MongoDB Enterprise versions are supported at once; see Database Engine Versions for the catalog and its dates.

What it suits​

The service fits applications that need horizontal scale, a flexible schema, or large-scale data processing:

  • Mobile and backend systems
  • Analytics platforms
  • IoT workloads
  • Fintech systems
  • Digital platforms

If your data is strongly relational and your queries are join-heavy, a relational engine is usually the better fit — FPT Database Engine covers PostgreSQL, MySQL, MariaDB, and SQL Server.

Security posture​

Security is built into the service rather than bolted on:

  • Encryption of data at rest and in transit
  • Role-based access control with fine-grained permissions
  • VPC integration, so clusters sit inside your own network boundary
  • IP-based access control through Security Groups

Shared responsibility​

Managed does not mean unattended. The split is worth understanding before you design against the service.

FPT Cloud is responsible forYou are responsible for
Infrastructure and the platform it runs onYour data and what it contains
Core database operations — provisioning, patching, failoverSchema design and indexing strategy
Backup execution, monitoring collection, alert deliveryApplication access, credentials, and business logic
Service availability against the SLAChoosing an architecture that matches your availability needs

The practical consequence: FPT Cloud keeps the engine running, but a Single Node cluster has no failover no matter how well the platform behaves. That choice is yours, and it is made at provisioning time.

Next steps​