Before you use ApsaraDB for MongoDB sharded cluster instances, you must familiarize yourself with the limits on this instance architecture. This way, you can determine whether this architecture meets your business requirements.
Item | Limits on DynamoDB-compatible sharded cluster instances | Limits on MongoDB-compatible sharded cluster instances |
Instance deployment | Sharded cluster instances can be deployed only in specific regions and zones. For more information, see Availability in regions and zones. | |
Engine version | The MongoDB versions and storage engines of sharded cluster instances impose limits on each other. For more information, see MongoDB versions and storage engines. | |
Minor database version | None | If the minor version of an ApsaraDB for MongoDB sharded cluster 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 upgrade, 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 | Only Physical Backup and Logical Backup are supported. | |
Data restoration | Only data restoration to a new sharded cluster instance by backup point is supported. For more information, see Restore backup data to a new ApsaraDB for MongoDB instance by point in time. | |
Data security |
|
|
CloudDBA | CloudDBA is not supported. CloudDBA features include Performance, Real-time Performance, Sessions, Storage Analysis, and Slow Query Logs. | - |
Data migration and synchronization |
| |
Instance connection | The following methods can be used to connect to a sharded cluster instance:
| |
Recycle bin | The recycle bin feature is not supported. | |