Infrastructure for Backend Performances
Infrastructure scaling is the work of adding capacity to a backend by running more or larger machines behind load balancers. Vertical scaling enlarges one server, horizontal scaling adds more of them, and autoscaling adjusts the count automatically. Stateless services make horizontal scaling straightforward, while stateful ones need extra design.
Stage: Scale · Part of the Backend Performance roadmap · Last reviewed 19 November 2026
What to learn in Infrastructure
- Contrast vertical and horizontal scaling and name the limits of each
- Place a load balancer in front of stateless application servers
- Move session state out of the app server so it can scale horizontally
- Define an autoscaling rule based on CPU or request metrics
- Identify the single points of failure in a simple architecture
Infrastructure interview questions
Why should application servers be stateless to scale horizontally?
If a server keeps user state in local memory, a request must return to that same server, which limits balancing and loses data when it dies. Storing state in a shared database or cache lets any instance serve any request and be replaced freely.
When would you scale a backend vertically instead of horizontally?
Vertical scaling gives one machine more CPU, memory or disk, which is simple but hits hardware and cost ceilings and remains one failure point. Horizontal scaling adds more machines behind a load balancer, which scales further and tolerates failures but needs a stateless design.
Where Infrastructure fits in the Backend Performance roadmap
Infrastructure belongs to the Scale stage (advanced level). Plan for growth.
Other units in this stage
Back to the full Backend Performance roadmap