ApsaraDB for MongoDB standalone instances provide a cost-effective deployment architecture. They are suitable for storing non-core data for purposes such as development, testing, learning, and training.
Precautions
Standalone instances take a long time to recover from failures and are not covered by a Service-Level Agreement (SLA).
Limits
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.
To use standalone instances that run MongoDB 4.2 or later, you must submit a ticket to request access.
Standalone instances are supported by default for MongoDB 4.0 and MongoDB 3.4. You can create standalone instances of these versions as needed.
ImportantInstances that run MongoDB 3.4 have been unavailable for purchase since January 1, 2023. For more information, see [Notice] End of sale for MongoDB 3.4 instances as of January 1, 2023.
Architecture
A standalone instance consists of a single node that is used to read and write data.
Standalone instances provide the operations and maintenance (O&M) support and kernel optimization of ApsaraDB for MongoDB at a lower price. You can select instance specifications based on your business scenario to reduce costs. For more information about specifications, see Standalone instance types.
FAQ
Q: Do standalone instances provide high availability?
A: No, they do not. A standalone instance has only one replica. In extreme cases, 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 and synchronization, or point-in-time recovery to a new instance?
A: No, they do not. By default, standalone instances do not support operation logs (oplogs). Therefore, these features are not supported.