Why should you care?

Global products need local reads, huge data volume, and uptime. Architecture diagrams must show how a write in Mumbai reaches durability and how a read in Singapore is routed.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

// Topology introspection from mongos
sh.status()
db.adminCommand({ listShards: 1 })
db.adminCommand({ getClusterParameter: "changeStreamOptions" }) // may vary by version
// App connection essentials:
// - multiple mongos hosts
// - retryWrites=true
// - appropriate readPreference / writeConcern

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• sh.status and listShards reveal the live topology.
• Apps must use resilient URIs and concerns.
• Each shard is itself a replica set.
• Planning failure domains (rack/AZ/region) is part of architecture, not an afterthought.

Practice next

1. Draw boxes: App → mongos → shards(RS) + config RS.
2. Mark where your shard key lives in queries.
3. Decide RPO/RTO and writeConcern majority.
4. Add a DR region to your diagram.
5. List three queries that must be shard-targeted.

Remember

Shards + replicas + config + mongos = cluster. Design for failure domains. Connection settings are part of architecture.

Multi-region SaaS backbone

A B2B platform runs sharded clusters with replica sets per shard and regional mongos.

Outcome: Tenants get HA and scale without a rewrite at 10× growth.