ApsaraDB for MongoDB standalone instances use a single-node architecture designed for development, testing, learning, and training workloads. Do not use standalone instances in production. They have no high availability and are not covered by a Service-Level Agreement (SLA).
Single-node architecture
A standalone instance runs on a single node that handles both read and write operations.
-
Low cost: Select the instance type that fits your workload to minimize cost. See Standalone instance types.
-
Managed operations: ApsaraDB for MongoDB handles operations and maintenance (O&M) and kernel optimization, even for standalone instances.
Limitations
-
No high availability: A single-node instance has no redundancy. In a worst-case failure, expect a service interruption of about 30 minutes. For production workloads, use replica set or sharded cluster instances instead.
-
No oplog support: Standalone instances do not support operation logs (oplogs) by default. Without oplogs, incremental data migration, data synchronization, and point-in-time recovery are not supported.
-
Limited region and zone availability: Standalone instances are not available in all regions and zones. See Supported regions and zones.
-
MongoDB version requirement: Standalone instances running MongoDB 4.0 and 3.4 are discontinued. Create an instance running MongoDB 4.2 or later.