When we don’t do Partition & do Sharding (Matrix 3rd quadrant) then it is complete data replica. It totally depends on your business requirements, Quadrant 3 is more suitable when data can be fit in single database server but read traffic is high & you need data base availability.
Really confused about the difference, could it be correct if i say database sharding is database replication, However, if i say that, it would be wrong because a shard might contain records not available in another shard.
Th final matrix is totally on point, Vivek!
Thankyou Raul 🙌
Very insightful 👍!!
Revisiting the article and found out I missed to like it :D
Thanks for this one!
Informative & succinct, Vivek !
So, it means that in sharding, we are just having replica of data while in partitioning, the dataset is divided ?
When we don’t do Partition & do Sharding (Matrix 3rd quadrant) then it is complete data replica. It totally depends on your business requirements, Quadrant 3 is more suitable when data can be fit in single database server but read traffic is high & you need data base availability.
Designing Data-Intensive Applications - Pg.199
Terminological confusion
What we call a partition here is called a shard in MongoDB, Elasticsearch,
and SolrCloud; it’s known as a region in HBase, a tablet
in Bigtable, a vnode in Cassandra and Riak, and a vBucket in
Couchbase. However, partitioning is the most established term, so
we’ll stick with that.
It’s very insightful 😇
Really confused about the difference, could it be correct if i say database sharding is database replication, However, if i say that, it would be wrong because a shard might contain records not available in another shard.
Yes replication can not be called shardjng.