Different properties of an item are stored in different partitions. One partition holds data that is accessed more frequently, including product name, description, and price.
Vertical partitioning operates at the entity level within a data store, partially normalizing an entity to break it down from a wide item to a set of narrow items. It is ideally suited for column-oriented data stores such as HBase and Cassandra.
- Optimized querying: Properties can be stored together based on access frequency, or how frequently they are queried together. Therefore, efficiently separating slow-moving data from the more dynamic one. Moreover, slow-moving data is a good candidate for an application to cache.
- Security: Sensitive data can be stored in a separate partition with additional security controls.
- Contention: It can reduce the amount of concurrent access that's needed.