Before you use ApsaraDB for MongoDB, you must familiarize yourself with the limits on ApsaraDB for MongoDB instance architectures. This way, you can select the instance architectures that best suit your business scenarios.
Standalone instances
Item | Limits |
Instance deployment | Standalone instances can be deployed only in specific regions and zones. For more information, see Available regions and zones. |
Engine version | Standalone instances support only MongoDB 3.4 and 4.0. Important Instances that run MongoDB 3.4 have been unavailable as of January 1, 2023. For more information, see [Notice] End of sale for MongoDB 3.4 instances as of January 1, 2023. |
Database connection | Encryption features cannot be enabled or disabled for internal network access. |
Data backup | Only Snapshot Backup is supported. Note A snapshot is a point-in-time backup of disk data. |
Data restoration |
|
Service availability | High availability features are not supported. These features include primary/secondary switchover, role switching, and instance migration across zones. |
Data security |
|
Log management | Log management features are not supported. These features include Slow Query Logs, Error Logs, and Running Logs. |
CloudDBA |
|
Data migration and synchronization |
|
Replica set instances
Item | Limits |
Instance deployment | Replica set instances can be deployed only in specific regions and zones. For more information, see Available regions and zones. |
Minor engine version | If the minor version of an instance expires or is not maintained, ApsaraDB for MongoDB automatically updates the minor version of the instance to the latest version when you perform specific operations. This ensures greater instance performance and stability. These operations include version upgrades, data migration, configuration change, and data restoration. |
Database connection | Replica set instances that run MongoDB 4.4 or later do not support network type switch from the classic network to VPC. |
Data backup |
|
Data security |
|
Log management | None |
CloudDBA | None |
Data migration and synchronization |
|
Sharded cluster instances
Item | Limits |
Instance deployment | Sharded cluster instances can be deployed only in specific regions and zones. For more information, see Available regions and zones. |
Minor engine version | If the minor version of an instance expires or is not maintained, ApsaraDB for MongoDB automatically updates the minor version of the instance to the latest version when you perform specific operations. This ensures greater instance performance and stability. These operations include version upgrades, data migration, configuration change, and data restoration. |
Data read and write | You can only read data from the admin database of a sharded cluster instance. You cannot write data to the admin database. |
Data backup | Sharded cluster instances support Physical Backup and Logical Backup. |
Data restoration | Only point-in-time data restoration to a new instance is supported. For more information, see Restore backup data to a new ApsaraDB for MongoDB instance by point in time. |
Data security |
Note DynamoDB-compatible sharded cluster instances support only VPC. For information about how to create a VPC, see Create and manage a VPC. |
CloudDBA | CloudDBA is not supported for DynamoDB-compatible sharded cluster instances. CloudDBA features include Performance, Real-time Performance, Sessions, Storage Analysis, and Slow Query Logs. |
Data migration and synchronization |
|
Recycle bin | Sharded cluster instances do not support the recycle bin feature. |