Overview
Direct Answer
Vertical scaling, also known as scale-up, is the process of adding computational resources—such as CPU cores, RAM, or storage capacity—to a single existing server or instance to increase its processing capability. This contrasts with horizontal scaling, which distributes load across multiple machines.
How It Works
When a system experiences performance bottlenecks, administrators upgrade the underlying hardware or allocate additional virtual resources to the existing instance without changing the application architecture. The system typically requires a restart or brief downtime to recognise and utilise the new resources. Applications continue to operate on the same machine, with no redistribution logic or load balancing required.
Why It Matters
Organisations favour this approach for its simplicity—no architectural redesign, no distributed system complexity, and no code changes needed. It provides immediate relief for resource-constrained applications and remains cost-effective for workloads that do not demand extreme scalability or high-availability requirements.
Common Applications
Databases, particularly relational systems requiring single-point consistency, frequently benefit from vertical scaling. Legacy monolithic applications and stateful services with tight data locality requirements commonly employ this strategy to handle growing user bases without refactoring.
Key Considerations
This approach has inherent limits; physical or cloud provider constraints eventually prevent further upgrades. Extended downtime during resource reallocation and single points of failure make it unsuitable for mission-critical systems requiring continuous availability.
More in DevOps & Infrastructure
Blue-Green Infrastructure
CI/CDMaintaining two identical production environments to enable instant switching between versions.
Distributed Tracing
ObservabilityA method of tracking requests as they flow through distributed systems to diagnose latency and failure points.
Error Budget
ObservabilityThe maximum amount of time a service can be unavailable within a given period based on its SLO.
Helm
Containers & OrchestrationA package manager for Kubernetes that simplifies the deployment and management of applications using charts.
Horizontal Scaling
CI/CDAdding more machines or nodes to a system to handle increased load.
Logging
ObservabilityThe practice of recording events, errors, and system activities for debugging, auditing, and analysis.
GitOps
Infrastructure as CodeAn operational framework using Git repositories as the single source of truth for declarative infrastructure and applications.
Ansible
Infrastructure as CodeAn open-source automation tool for configuration management, application deployment, and task automation.