Kubernetes Horizontal vs Vertical scaling
parameter |
horizontal scaling |
vertical scaling |
---|---|---|
Main Aim |
Increasing/decreasing the number of machines |
Adjusting the CPU and memory on existing machine |
Best Use in |
stateless applications |
stateful applications |
Scalability |
High |
Limited to maximum resources |
Complexity |
High |
Lower |
Tool Used |
HAP ( Horizontal Pod Autoscaler ) |
VAP ( Vertical Pod Autoscaler ) |
Tolerance in fault cases |
Higher, one fault doesn’t effect other |
lower, one fault can effect other |
cost |
Can be cost-effective |
Can lead to higher costs |
Kubernetes Horizontal vs Vertical scaling
In Kubernetes, scaling is the most fundamental concept that makes sure applications run smoothly and consistently. Just consider a scenario where low resources are causing the application to freeze under the existing load. One potential solution is to manually assign the resources whenever this occurs, but it will take a lot of time. This is the place where scaling(moreover autoscaling) comes into action: the ability to scale applications to meet varying needs efficiently is one of the key features of Kubernetes.