Visualizers
Learn by moving things
Interactive explainers for the ideas behind retrieval, embeddings, and agents. A formula tells you what is true; dragging a vector shows you why. Each one also appears inside the article it belongs to, and runs entirely in your browser, so drag, poke, and break it.
The DNS lookup chain
From: DNS: The Internet's Phone Book →Who does the resolver ask? It is passed along a chain like directory assistance: root (who runs .com?), then the .com servers (who runs the domain?), then the authoritative server (the address).
Your resolver does not know guptasachinn.com yet, so it starts asking around.
The load balancer: request to server
From: Load Balancers, Up Close →Request goes to load balancer goes to server, one example at a time. It cycles through the strategies, round-robin, least-connections, and random, so you can watch each one distribute traffic. A down server is always skipped.
round-robin: deal to each server in turn. Either way, a server that stops answering (server 3) is skipped until it recovers.
Health checks: is everyone still there?
From: Load Balancers, Up Close →The load balancer pings each server every few seconds. Server 2 misses two checks, gets pulled out of rotation so no request reaches a dead machine, then answers again and is put back.
Every few seconds the load balancer pings each server. All three answer, so all three take requests.