Each DDS cluster is an independent document database. A sharded cluster consists of mongos, config, and shard.
Data read and write requests are forwarded by mongos. A mongos reads configuration settings from configs and allocates the read and write requests to shards, making it easy to cope with high concurrency scenarios. In addition, config and shard with the three-node architecture can ensure high availability. Figure 1 shows the DDS cluster architecture.
Figure 1 Cluster architecture
- mongos is deployed on a single node. To realize load balancing and automatic failover, you can provision multiple mongos. A single cluster supports 2 to 12 mongos.
- shard is deployed with an architecture of three-node replica set. A single cluster supports 2 to 12 shards.
- config is mandatory in a cluster instance. It stores instance configuration information and consists of one replica set.
- mongos and shard nodes cannot be added using native commands but can be scaled out on the DDS console.
- You cannot connect to config and shard. Data operations can only be delivered by connecting to mongos.
- Cluster DB instances can only be created with the DDS console. Currently, a three-node replica set cannot be directly upgraded to a cluster.