Srijan Shukla
Back to blog
•
5 min read
networking

Disclaimer: I have found it a lil tough to translate my mental model about XYZ topic in words to juniors. I’m able to explain it to them, but I’m making up stuff on the fly when I do that. So, I’m using LLM to do this now. Most of what you see below is LLM. I have pestered LLMs enough till I like what I read.

Here’s an analogy-driven breakdown of networking from IP packets to HTTP, tailored for a junior SRE working in the cloud. Think of it as a global postal system for data:

🌍 The Postal System Analogy

Imagine the internet as a worldwide postal service. Data is sent in “packets” (envelopes), and each layer of the network adds a specific capability. Let’s break it down:

1. IP (Internet Protocol) = Postal Addresses (Layer 3)

  • Purpose: Get packets to the right “city” (network) and “street” (device).
  • How it works:
    • Every device has an IP address (e.g., 192.168.1.1), like a home address.
    • Routers act as post offices: They read the IP address and forward packets toward the destination.
  • Key trait: Best-effort delivery.
    • “We’ll try to deliver your letter, but no guarantees if it gets lost.”
  • Analogy: Writing a destination address on an envelope.
  • Cloud relevance:
    • VPCs (Virtual Private Clouds) are gated neighborhoods-only allowed traffic gets in/out.
    • NAT Gateways are mailrooms: They mask internal IPs (e.g., all office mail uses one return address).

2. TCP vs. UDP = Delivery Guarantees (Layer 4)

  • TCP (Transmission Control Protocol) = Registered Mail
    • Purpose: Reliable, error-checked delivery.
    • How it works:
      • “Did you get my letter? Please confirm!” (Acknowledgements and retries).
      • Reassembles packets in order (like numbering pages in a letter).
    • Use when: Web traffic, file transfers (e.g., HTTPS, SSH).
  • UDP (User Datagram Protocol) = Postcard
    • Purpose: Fast, fire-and-forget delivery.
    • How it works:
      • No confirmations or retries.
      • Packets may arrive out of order or get lost.
    • Use when: Streaming, gaming, VoIP (e.g., video calls, live broadcasts).
  • Cloud relevance:
    • Load Balancers = Sorting centers: Distribute TCP/UDP traffic across servers.

3. DNS = The Phone Book

  • Purpose: Translate human-friendly names (e.g., google.com) to IP addresses.
  • How it works:
    • You ask, “What’s the IP for api.example.com?” → DNS servers reply, “It’s 203.0.113.5.”
  • Analogy: Looking up a friend’s address in a phone book before mailing them.
  • Cloud relevance:
    • Route 53 (AWS) or Cloud DNS (GCP) are digital phone books managed by your cloud provider.

4. TLS/SSL = Sealed Envelopes

  • Purpose: Encrypt data so only the recipient can read it.
  • How it works:
    • Establishes a secure “handshake” to agree on encryption keys.
    • Data is scrambled (like a sealed envelope) during transit.
  • Analogy: Sending a locked safe instead of a postcard. Only the recipient has the combo.
  • Cloud relevance:
    • Certificates (e.g., ACM in AWS) are digital “locks” issued by trusted authorities.

5. HTTP = The Letter’s Content (Layer 7)

  • Purpose: Define how applications communicate (e.g., request a webpage, send API data).
  • How it works:
    • HTTP Requests: “GET me the homepage.”
    • HTTP Responses: “Here’s the HTML/CSS/JS for that page (status 200).”
  • Analogy: The language and format of the letter (e.g., English, business format).
  • Cloud relevance:
    • API Gateways = Receptionists: Route HTTP requests to backend services (e.g., Lambda, EC2).
    • CDNs = Local post offices: Cache HTTP content closer to users for faster delivery.

🎯 Key Takeaways for Cloud SREs

  1. IP = Addresses and routing (VPCs, subnets, NAT).
  2. TCP/UDP = Delivery guarantees (load balancers, security groups).
  3. DNS = Name-to-IP translation (Route 53, Cloud DNS).
  4. TLS = Encryption (certificates, HTTPS).
  5. HTTP = Application communication (APIs, CDNs, serverless).

🌟 Workflow Example: Visiting a Website

  1. DNS Lookup: “Where is example.com?” → IP address.
  2. TCP Handshake: “Hello, server! Let’s establish a connection.”
  3. TLS Handshake: “Let’s agree on a secret code.”
  4. HTTP Request: “GET /homepage” → Server responds with the webpage.

💡 Memorable Insight

“Networking is like sending a letter:

  • Address it (IP),
  • Choose postage (TCP/UDP),
  • Look up the address (DNS),
  • Seal it (TLS),
  • Write the message (HTTP).”**