Vertical Partitioning
In the preceding chapters of this book, we went from grasping the fundamentals of DynamoDB to exploring interactions and adopting a NoSQL mindset. We dove into the nuances of data modeling and optimizing data models as per our access patterns, considering the application’s read- or write-heavy requirements.
Our exploration also covered the misconception that NoSQL implies non-relational, clarifying that while data is always relational, its representation and organization in NoSQL systems differ. We examined the approaches of single-table design and multi-table design, emphasizing the mantra Data that needs to be accessed together must be stored together. Balancing performance and cost considerations is crucial in deciding between these approaches.
This chapter mostly focuses on single-table design – specifically, on the vital concept of data modeling known as Vertical Partitioning. At a high level, vertical partitioning involves breaking items...
