Which database( embedded or normalized) is better in terms of scalability?

330 Views Asked by At

We know that MongoDB uses sharding to provide horizontal scaling. These clusters support deployments with large data sets and high-throughput operations. Sharding allows users to partition a collection within a database to distribute the collection's documents across a number of mongod instances or shards. But how can sharding address scalability on an embedded and normalized collections? Which database( embedded or normalized) is better in terms of scalability?

1

There are 1 best solutions below

0
Tom Slabbaert On

But how can sharding address scalability on an embedded and normalized collections?

It can't it will be a nightmare to maintain most likely, depending on your usage.

Which database( embedded or normalized) is better in terms of scalability?

Most likely the normalized approach will perform much better, each has it's pro's and con's however if your embedded data has updates performed on it I would personally recommend not to use this approach. Especially at scale. I also find that in many cases a structural change of the data can solve many of these issues, worth considering.

Obviously these are very broad statements, and should be considered within context of your needs.