ApsaraDB for MongoDB:Getting started

ApsaraDB for MongoDB supports multiple flexible deployment architectures to meet business scenario requirements. Architectures:

• Standalone architecture

  This architecture applies to development, testing, education, and scenarios where non-core enterprise data is stored. You can select the instance specifications that best suit your business scenarios to minimize costs. For more information, see Standalone instances.

• Replica set architecture

  This architecture suits burst traffic scenarios that require significantly more reads than writes or temporary activities. A replica set instance consists of a primary node that supports read/write operations, one, three, or five high-availability secondary nodes, a hidden node, and up to five optional read-only nodes. You can add or remove secondary and read-only nodes based on your business requirements. For more information, see Replica set instances.

• Sharded cluster architecture

  This architecture suits scenarios that require highly concurrent read/write operations. A sharded cluster instance consists of multiple three-node replica sets. Each replica set contains three nodes in primary/secondary mode and up to five optional read-only nodes. A sharded cluster instance consists of three components: mongos, shard, and ConfigServer. You can specify the number and specifications of mongos nodes and shards to create sharded cluster instances that have different service capabilities. For more information, see Sharded cluster instances.