Index of every page on this site: llms.txt
All skills
proyecto26 avatar

/load-balancing

@228d57d
Run it yourself

This skill should be used when the user adds a "load balancer", asks about "L4 vs L7" (transport vs application layer), picks a balancing algorithm ("round robin", "least connections", "weighted", "IP hash"), configures "health checks", needs "sticky sessions" / "session affinity", adds a "reverse proxy", does "SSL/TLS termination", spreads "traffic distribution" across an "autoscaling group", or wants a stateless web tier behind a single entry point. Use it whenever a design has more than one server behind one address, or a single box is the entry-point bottleneck or SPOF, even if the user doesn't say "load balancer".

Use this Skill: https://skilld.dev/gh/proyecto26/system-design-skills/load-balancing

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

referencesprovidersazure.md

≈536 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Load balancing — Azure

Service mapping

  • Azure Load Balancer — managed L4 (TCP/UDP); high throughput, low latency, source-IP preservation, public or internal. The L4 default within a region.
  • Application Gateway — managed L7; path/host routing, TLS termination, cookie-based affinity, autoscaling, with an optional WAF tier. The HTTP(S) default when you need content routing in-region.
  • Azure Front Door — global L7 edge: anycast entry, TLS offload, path/host routing, caching, and WAF at the edge (cross-region steering + CDN, → content-delivery). Use for global apps, not single-region balancing.
  • Traffic Manager — DNS-based global routing (priority/weighted/geo/perf); like Route 53, it steers between endpoints, it is not an L4/L7 data-path LB.
  • VM Scale Set — the autoscaling fleet the LB/App Gateway balances over.

When to pick which

Azure Load Balancer for L4 TCP/UDP throughput within a region; Application Gateway for in-region L7 HTTP routing + WAF; Front Door for global edge routing/caching; Traffic Manager when DNS-level endpoint selection is enough.

Limits / things that bite (verify against current docs)

  • Application Gateway v1 had manual sizing; v2 autoscales — confirm you're on v2 for elastic load, and note warm-up time on sudden spikes.
  • Basic Load Balancer lacks features/SLA of Standard and is being retired — use Standard.
  • L4 Load Balancer does no TLS termination or content routing (that's App Gateway/Front Door); don't expect L7 behavior from it.
  • Probe (health-check) interval/threshold config drives eviction speed and flap — set deliberately; an unhealthy probe drops the backend from rotation.

Pitfalls

  • Reaching for Front Door for a single-region app (over-engineering + cost) — App Gateway or Load Balancer suffices.
  • Using cookie affinity on App Gateway instead of externalizing session state, then losing sessions on scale-in.
  • Confusing Traffic Manager (DNS steering) with an actual data-path balancer.
  • Lock-in: App Gateway/Front Door rules and WAF policies don't port to other clouds.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill is a set of architectural guidelines and reference materials for load balancing strategies. It contains no executable code, remote downloads, or dangerous commands.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at 228d57d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for proyecto26/system-design-skills/load-balancing