Questions about MongoDB
Why should I use MongoDB in Managed Service for MongoDB rather than my own VM-based installation?
Managed Service for MongoDB automates routine database maintenance:
- Quick DB deployment with the necessary available resources.
- Data backup.
- Regular software updates.
- DB cluster failover.
- Database usage monitoring and statistics.
What happens to a cluster if one of its hosts fails?
If there are more than one replica in the database cluster, it will continue working if a host fails.
The only way data may be lost is if the cluster's only host fails.
Can I deploy a MongoDB cluster in multiple availability zones?
Yes. A database cluster may consist of hosts that reside in different availability zones and even different availability regions.
How do I back up MongoDB clusters?
Backups are created every 24 hours and stored for seven days after being created. You can restore data only as of backup creation time.
How does replication work for MongoDB?
Managed Service for MongoDB uses the standard MongoDB replication mechanism: if a cluster has multiple active hosts, one of them is automatically selected as the primary server for handling write requests.
For more information about how replication works in MongoDB, read the DBMS documentation.
What limitations are imposed on MongoDB database clusters?
MongoDB clusters are subject to the following limitations:
- Each cluster may have a maximum of five hosts.
- The maximum storage capacity for each MongoDB cluster is 512 GB.
For more information about Managed Service for MongoDB limits, see Quotas and limits.