liveBook · Manning

Load balancing

As explained in Tech Startup Toolkit

Load balancing is the distribution of incoming workload across multiple servers to prevent any one server from exceeding its capacity.

Load balancing spreads a website’s workload across multiple servers so one machine does not exceed its capacity and crash. It matters when a site changes from static information into an interactive service: thousands of people may need service at the same time. section 2.1 section 15.2

A traffic spike is a real product problem

A Super Bowl advertisement sent viewers to Victoria’s Secret’s website at once. The single server was overloaded and the site crashed. The practical lesson is blunt: a successful promotion can break the very service it is meant to promote unless capacity is shared across servers. section 2.1

The same need appears when the site carries consequential interactions. Fidelity Investments wanted customers to access 401(k) accounts directly without repeating the failure of a site overwhelmed by simultaneous visitors. Load balancing is therefore not just infrastructure jargon; it protects a customer-facing service at the moment demand arrives. section 2.1

A useful way to judge a load-balancing opportunity is to ask:

  • Will many visitors arrive together rather than at a predictable, manageable pace? section 2.1
  • Would a crash interrupt an interaction people need to complete, such as a financial transaction? section 2.1
  • Is there a real market willing to adopt a tool that brings multiple web servers into service? section 15.2

Load balancing can also define a market rather than merely improve a product. As the Web became a place for applications and transactions, website load balancing emerged as a need. A tool that pulled an array of web servers into service met that need, illustrating product–market fit: the product mattered because a large and growing market had the problem. section 15.2 section 2.1

The uncomfortable startup lesson is that technical usefulness alone is not the whole story. A capable product can become highly valuable when it addresses a broad market, while team quality or product polish does not substitute for market demand. Keep the takeaway simple: prevent the crash, but first make sure enough customers care about preventing it. section 15.2

How Tech Startup Toolkit covers it

How deep it goes
Explains the operational purpose through outage and customer-demand cases, without detailing traffic-routing mechanics.
Examples
Uses Victoria’s Secret’s Super Bowl crash, Fidelity’s 401(k) access, and WebSpective’s web-server array.
What it assumes
Introduces the problem from zero through single-server crashes and concurrent visitor demand.
What you can do after
Evaluate/understand when simultaneous visitor demand makes distributing work across servers commercially valuable.
How it connects
Connects load balancing with web applications, server capacity, distributed computing, and product–market fit.

Also explained in

Compare how 14 books explain load balancing →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Tech Startup Toolkit. The section links point to the parts of the book it draws on.