Database Reference
In-Depth Information
Utilizing sharding
Sharding is the solution to address scaling issues in MongoDB. Using sharding, developers
can horizontally scale the database over multiple servers. The same dataset is divided over
multiple servers. Each individual server calls the shard; it is an independent database. All
shards together make the single logical database.
The following diagram shows you the sharding process:
Sharding solves the problem of high overload and large datasets. While inserting or reading
data, the client or application needs to access only one shard and not all shards. Hence, this
change will horizontally scale the throughput and overload. Consequently, the database can
support more operations.
On the other hand, by dividing the whole database over different servers, it reduces the
amount of data that each server should store. Hence, each shard holds only a specific part
of the whole database. As a result, to store 1 TB database using sharding, you can have four
different servers, each having a storage of 256 GB. By adding more shards, you can reduce
the storage size of each server.
