PracHub
QuestionsPremiumCoachesLearningGuidesInterview Prep
|Home/System Design/Amazon

Design a High-Availability Load Balancer

Last updated: May 30, 2026

Quick Overview

This question evaluates understanding of load balancing, high-availability architecture, distributed systems, networking, reliability, and operational concerns such as health checks, weighted routing, graceful instance removal, and observability.

  • hard
  • Amazon
  • System Design
  • Software Engineer

Design a High-Availability Load Balancer

Company: Amazon

Role: Software Engineer

Category: System Design

Difficulty: hard

Interview Round: Onsite

Design a load balancer that routes HTTP and HTTPS traffic to a fleet of backend service instances across multiple availability zones. The system should support high request volume, low added latency, backend health checks, weighted traffic distribution, graceful removal of unhealthy or draining instances, observability, and no single point of failure. Discuss the API or configuration model, high-level architecture, request flow, routing algorithms, failure handling, scaling strategy, and key trade-offs.

Quick Answer: This question evaluates understanding of load balancing, high-availability architecture, distributed systems, networking, reliability, and operational concerns such as health checks, weighted routing, graceful instance removal, and observability.

Related Interview Questions

  • Design a Log Collection System - Amazon (medium)
  • Design Human Avoidance for Warehouse Robots - Amazon (medium)
  • Design a Ride-Hailing Matching System - Amazon (medium)
  • Design a replicated cloud storage service - Amazon (hard)
  • Design a cloud database write path and recovery - Amazon (hard)
Amazon logo
Amazon
May 9, 2026, 12:00 AM
Software Engineer
Onsite
System Design
4
0

Design a load balancer that routes HTTP and HTTPS traffic to a fleet of backend service instances across multiple availability zones. The system should support high request volume, low added latency, backend health checks, weighted traffic distribution, graceful removal of unhealthy or draining instances, observability, and no single point of failure. Discuss the API or configuration model, high-level architecture, request flow, routing algorithms, failure handling, scaling strategy, and key trade-offs.

Solution

Show

Submit Your Answer

Sign in to leave a comment

Loading comments...

Browse More Questions

More System Design•More Amazon•More Software Engineer•Amazon Software Engineer•Amazon System Design•Software Engineer System Design
PracHub

Master your tech interviews with 8,500+ real questions from top companies.

Product

  • Questions
  • Learning Tracks
  • Interview Guides
  • Resources
  • Premium
  • For Universities
  • Student Access

Browse

  • By Company
  • By Role
  • By Category
  • Topic Hubs
  • SQL Questions
  • Compare Platforms
  • Discord Community

Support

  • support@prachub.com
  • (916) 541-4762

Legal

  • Privacy Policy
  • Terms of Service
  • About Us

© 2026 PracHub. All rights reserved.