ApsaraDB for MongoDB standalone instances are a cost-effective deployment architecture that is suitable for storing non-critical business data in scenarios such as development, testing, learning, and training.
Precautions
Standalone instances can take a long time to recover from failures and are not covered by a Service-Level Agreement (SLA).
Limits
Standalone instances are not available in all regions and zones. For a list of supported regions and zones, see Supported regions and zones.
Standalone instances that run MongoDB 4.0 and 3.4 are discontinued. To use a standalone instance, create an instance that runs MongoDB 4.2 or later.
Single-node architecture
A standalone instance consists of a single node that is used for both read and write operations.
Standalone instances offer the operations and maintenance (O&M) support and kernel optimization of ApsaraDB for MongoDB at a low price. You can select an instance type that fits your business scenario to reduce costs. For more information, see Standalone instance types.
FAQ
Q: Do standalone instances provide high availability?
A: No, they do not. A standalone instance has only one node and does not provide high availability. In a worst-case scenario, a failure can cause a service interruption of about 30 minutes. We recommend that you use replica set or sharded cluster instances in production environments.
Q: Do standalone instances support incremental data migration, synchronization, or point-in-time recovery?
A: No, they do not. Standalone instances do not support these features because they do not support operation logs (oplogs) by default. Without oplogs, incremental data migration, synchronization, or point-in-time recovery is not possible.