Common load‑balancing strategies include round‑robin, least connections, weighted variants, IP‑hash/sticky sessions, and consistent hashing. Load balancers can work at L4 (TCP/UDP) or L7 (HTTP) and use health checks to avoid unhealthy nodes.
Advanced answer
Deep dive
Expanding on the short answer — what usually matters in practice:
Explain the "why", not just the "what" (intuition + consequences).
Trade-offs: what you gain/lose (time, memory, complexity, risk).
Edge cases: empty inputs, large inputs, invalid inputs, concurrency.
Examples
A tiny example (an explanation template):
// Example: discuss trade-offs for "load-balancing-strategies?"
function explain() {
// Start from the core idea:
// Round Robin, Least Connections, IP Hash. Used to distribute traffic evenly across multiple
}
Common pitfalls
Too generic: no concrete trade-offs or examples.
Mixing average-case and worst-case (e.g., complexity).