Index

Module 03 · DevOpsRegions, networks and doors

Load Balancing & DNS (the operator’s half)

Load Balancing & DNS
Load Balancing & DNS · Open board

The two dispatchers: DNS picks which endpoint, the load balancer picks which instance. This lesson is what both jobs look like once real traffic, real failures, and a 3am page show up.

Before you start. You already know how a name resolves - recursive resolver, root, TLD, authoritative server (DNS Resolution), and what’s on the wire (DNS on the wire) - and you’ve met the L4/L7 split - an L4 balancer sees only which address and door a connection is headed for, an L7 one opens the request and reads what is being asked - and built a toy balancer of your own (The chai stall that got famous (load balancing), S2 · Build a Load Balancer). This lesson is what both dispatchers do in production, where they fail, and why the failures look nothing alike.

Continue reading with a plan

The first three lessons of every track are free. This lesson is included with a plan, which unlocks every lesson, board, video, lab and paper for one price.

View plans →Already a member? Sign in

Lab

Every algorithm looks identical on the benchmark. Which one is still standing when two requests in a hundred cost sixty times the rest?

Drag How much more the expensive requests cost to the far end, then switch tabs and read p99 under What the caller waited.

Open The load balancer →

Related paper

Review DevOps →

Saved in this browser, and to your account when you sign in.