Denormalization

We have already discussed how storage in columnar datastores doesn't fit into the traditional definitions of normalization. In traditional RDBMSs, minimizing redundancy is an important objective, which gave rise to the different normal forms. Normalization in traditional database design was largely driven by the need to save space, which in turn was driven by the monolithic nature of database servers. As distributed databases came along, the bandwidth became the bottleneck. Your normalized data could end up storing related data items in distant nodes. Even if you saved a few bytes, if you had to access the network three times instead of once, that would give terrible performance. Consequently, in the distributed world, disk ...

Get Google Cloud Platform for Architects now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.