Can someone explain why they say db replication is more ideal for read scalability while sharding is more ideal for write scalability?
From my current understanding:
- replication allows read traffic to be distributed among several replicas rather than a single node, increasing read traffic. Does this not also apply to write traffic?
- sharding allows a very large db node (say for example 10 TB) to be split into several smaller nodes, which allows traffic/queries to be a lot faster (since it does not need to search through 10 TB of data). Does this not apply to both read and write traffic?
New contributor
Joshua Choe is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.