- query throughput and response times -
- adding resources to support database operations - vertical scaling - scaling up - its own set of limits
- horizontally partitioning a table - more compute capacity - serve incoming queries - faster query response times and index builds
- a network of smaller, cheaper servers vs one big server
- high availability at a low cost than vertical scaling
Business applications that rely on a monolithic RDBMS hit bottlenecks as they grow. With limited CPU, storage capacity, and memory, query throughput and response times are bound to suffer. When it comes to adding resources to support database operations, vertical scaling (aka scaling up) has its own set of limits and eventually reaches a point of diminishing returns.