⬆️Vertical Scaling

NEW

Also known as: Scale Up

Vertical scaling increases capacity by adding CPU, memory, or storage to an existing instance or node to handle greater load.

DESCRIPTION

Vertical scaling, or scale-up, boosts resources on a single machine. It’s straightforward and suits stateful systems and monoliths. Limits arise from hardware ceilings and single-point-of-failure risk. It may reduce management complexity compared to distributed architectures. Reserved high-memory or high-CPU instances can be cost-effective for certain workloads. Combine with failover and backups to mitigate risks.

ALTERNATIVE DEFINITIONS

Wikipedia

Vertical scaling (scaling up) means adding more resources to a single node, such as more CPU, memory, or storage, to handle increased workload.

Defines scale-up as increasing resources on one node.

Source

DigitalOcean

Vertical scaling means adding more power (CPU, RAM) to your existing machine.

Clear, concise contrast with horizontal scaling.

Source

Microsoft

Scaling up increases the size of a resource to add capacity, while scaling out adds more instances of the resource.

Compares scale-up vs scale-out in Azure guidance.

Source

RELATED TERMS

Autoscaling Scalability Capacity Planning High Memory Instances Single-node Database Elasticity Performance Tuning Load Balancing Virtual Machines

COMPETING TERMS

Horizontal Scaling

RELATIONS

• Broader: Scaling

KNOWLEDGE AREAS

Infrastructure Cloud Software Engineering Data Storage & Operations

TARGET AUDIENCE

Cloud Architect DevOps Engineer Software Developer Data Engineer Enterprise Architect

EXTERNAL SOURCES

• Wikipedia - Scalability
• Google Cloud - VM machine types for scale-up
• AWS - EC2 instance types for scaling
• Microsoft - Azure VM sizes scale-up options

TOP QUESTIONS

When is Vertical Scaling appropriate?

For stateful or monolithic apps where distribution is hard. It’s quick to implement and may reduce coordination complexity.

Category: Example

What are limitations of Vertical Scaling?

Hardware ceilings, single-node failure risk, and diminishing returns. It can be costly for high-end instances.

Category: Risk

Is Vertical Scaling cheaper than Horizontal Scaling?

Sometimes, for moderate loads. At scale, horizontal often wins due to commodity hardware and resilience benefits.

Category: Opinion

How does Vertical Scaling impact database performance?

More CPU and memory help single-node databases. But storage IOPS and contention may still require sharding or read replicas.

Category: Example

Can Vertical Scaling be automated?

Yes, with resize operations and scheduled maintenance windows. It’s less seamless than adding nodes horizontally.

Category: Overview

What monitoring is critical for Vertical Scaling decisions?

CPU, memory, disk I/O, and saturation metrics. Analyze trends and predict when to resize to avoid incidents.

Category: Testing

How to mitigate risks in Vertical Scaling?

Use backups, high-availability configurations, and failover instances. Plan maintenance windows for resizing.

Category: Requirements

Does Vertical Scaling affect licensing?

Yes, some software licenses scale with cores or memory. Factor licensing into total cost calculations.

Category: Risk

What’s a practical example of Vertical Scaling?

Increasing memory on a JVM-based service to reduce garbage collection pauses under sustained load.

Category: Example