sysdesign-load-balancers

Determine load balancer type, layer, TLS termination, and session handling for system designs.

Updated Apr 23, 2026

Search Tags:#routing #networking #cloud-architecture #system-design #load-balancer #high-availability

Ready to run

npx skills add https://github.com/danilods/matilha-sysdesign-pack --skill sysdesign-load-balancers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sysdesign-load-balancers
Source: https://github.com/danilods/matilha-sysdesign-pack/tree/main/skills/sysdesign-load-balancers
Command: npx skills add https://github.com/danilods/matilha-sysdesign-pack --skill sysdesign-load-balancers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine the right category, layer, TLS termination location, and session handling strategy to meet availability, performance, and security goals for a given workload.

Core Features & Use Cases

Classifies load-balancer needs into hardware, LBaaS, or software options based on environment and scale.
Chooses between L4 and L7 routing with explicit trade-offs and operational implications.
Guides TLS termination placement and sticky/session handling to align with compliance and app requirements.
Provides health-check and redundancy recommendations to avoid single points of failure in production deployments.

Quick Start

Determine the deployment context (cloud, on-prem, multi-region) and specify the traffic characteristics to select between hardware, LBaaS, or software load balancers, then configure TLS termination and session handling accordingly.

Frequently Asked Questions about sysdesign-load-balancers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I choose the right load balancer for my cloud or on-prem deployment?▼

Choosing the right load balancer requires classifying your needs into hardware, LBaaS, or software options based on your deployment environment and scale. This evaluates traffic characteristics and infrastructure integration to determine the optimal load balancer solution.

When should I use L4 vs L7 load balancing for high availability?▼

Selecting L4 or L7 load balancing depends on your routing trade-offs and operational implications. L4 offers faster network-level routing, while L7 enables application-level traffic steering, aligning with high-availability and performance goals for your workload.

How do I configure TLS termination and session handling for multi-replica services?▼

Configuring TLS termination and session handling requires evaluating compliance and application requirements. This guides optimal placement for TLS termination and sticky session handling to align with security policies and multi-replica service demands.

What are the best health-check and redundancy strategies to avoid single points of failure?▼

The best health-check and redundancy strategies involve planning health checks and configuring redundant load balancer deployments. This avoids single points of failure in production by integrating with existing observability and security policies.

Does a hardware load balancer offer better high availability than LBaaS for my system design?▼

A hardware load balancer offers robust high availability but lacks the elasticity of LBaaS. Choosing between hardware and LBaaS depends on your system design scale, cloud or on-prem environment, and specific traffic routing requirements.