Horizontal versus vertical scaling of a Java API: what hits the wall first?
PICTURE THIS: DATABASE INDEX
Simple meaning
Vertical scaling buys a bigger box until GC pauses, NUMA, and single-primary database limits appear.
WHY — Load balancer instead of guessing?
Why interviewers care about Load balancer:
contrast on Load balancer, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Vertical scaling buys a
bigger box until GC pauses, NUMA, and single-primary database limits appear.
- 2Horizontal scaling adds instances
behind a load balancer but needs stateless apps and a shared data store.
- 3You usually scale the
app out first and the database with replicas or sharding later.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Vertical scaling buys a bigger box until GC pauses, NUMA, and single-primary database limits appear. Horizontal scaling adds instances behind a load balancer but needs stateless apps and a shared data store.