- -1-Replica set out of the box
several nodes with automatic selection of the primary node in case of a failure
- -2-Sharding with a single parameter
Horizontal scaling across multiple shards with mongos routers.
- -3-Connection encryption
TLS certificates are issued and updated automatically by the platform.
- -4-Backup
Scheduled backups to an S3‑compatible storage; a new cluster can be deployed directly from the copy.
- -5-Standard protocol
mongosh, Compass, and all official drivers work without any changes.
- Default replica set
Several mongod nodes with replication; if the primary node becomes unavailable, the replica set automatically selects a new primary node — the drivers switch automatically.
- Sharded mode
For large volumes of data, the cluster is deployed as a set of shards (each with its own replica set) with config servers and mongos routers that transparently distribute requests.
- Automatic PKI
The operator issues and rotates TLS certificates for all nodes themselves — encryption is available without manual certificate management.
- Self-healingFallen nodes are recreated, and the cluster configuration is restored to the specified state — without manual intervention.
- Replicable storage — selectableThe storage class is specified during creation; the replicated class duplicates node data across multiple servers, and a disk failure does not result in replica loss.
-
Product data with a flexible schemacatalogs, profiles, configurations, content -
Event-based and log-like dataHigh write speed, document-based model -
Rapid product iterationsThe schema changes along with the code, without major migrations -
Growth without limitsStart with a replica set, enable sharding when the data grows beyond a single node
- 1Add the “MongoDB” service to your DevSpace: size, number of replicas, and for large volumes — sharding.
- 2Take the connection string from the service page — the credentials are generated automatically.
- 3Connect via mongosh or the driver — just like with any standard MongoDB.
FAQ
