ApsaraDB for MongoDB standalone instances are highly cost-effective and suitable for scenarios that do not require the storage of crucial business data. For example, you can use standalone instances in scenarios such as development, testing, learning, and training.
Standalone instances take a long time to recover from failures and have no Service Level Agreement (SLA) guarantees.
Standalone instances can be deployed only in specific regions and zones. For more information about the supported regions and zones, see Available regions and zones.
- Standalone instances only support MongoDB 4.0 and 3.4. You can create standalone instances that run MongoDB 4.0 or 3.4 based on your business requirements. For more information about how to create a standalone instance, see Create a standalone instance. 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.
- A standalone instance provides only one node that is used to read and write data.
- Standalone instances allow you to enjoy the O&M support and kernel optimization of ApsaraDB MongoDB at lower prices. You can select appropriate instance specifications for different business scenarios to reduce costs. For more information, see Instance types.
- Q: Do standalone instances provide high availability?
A: No, standalone instances do not provide high availability. A standalone instance has only one node, and a failure may cause a service interruption for around 30 minutes for the instance at worst. We recommend that you use replica set or sharded cluster instances in production environments.
- Q: Do standalone instances support incremental data migration, incremental data synchronization, and point-in-time data restoration to a new instance?
A: No, these features are not supported by standalone instances. By default, standalone instances do not support oplogs. As such, these features cannot be supported by standalone instances.