DevOps & InfrastructureCI/CD

Vertical Scaling

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

Distributed Tracing

Observability

A method of tracking requests as they flow through distributed systems to diagnose latency and failure points.

Ansible

Infrastructure as Code

An open-source automation tool for configuration management, application deployment, and task automation.

Logging

Observability

The practice of recording events, errors, and system activities for debugging, auditing, and analysis.

Chef

Infrastructure as Code

A configuration management tool using Ruby-based scripts to automate infrastructure setup and maintenance.

Rolling Update

CI/CD

A deployment strategy that gradually replaces instances of the previous version with the new version.

Runbook

Site Reliability

A documented set of procedures for handling routine operations and troubleshooting common issues.

Metrics

Observability

Quantitative measurements collected over time to track system performance, health, and business outcomes.

Monitoring

Observability

The continuous observation of system performance, availability, and health using automated tools and dashboards.