Skip to content

Exploring Networking🔗

Debug faster. Route correctly. Keep services connected.

Exploring Networking

Welcome to a practical guide to the networking that production actually runs on — the DNS lookups, load balancers, certificates, and routes that keep services reachable, and the diagnostics that get them back when they break.

The Problem🔗

It's 2am. The API is timing out. Users are getting 502s from the load balancer. You SSH in and... where do you even start? Is it DNS? A firewall rule? Latency? An expired TLS certificate?

Traditional networking courses start with the OSI model and packet-tracer simulations. This site starts with "How do I fix this production outage right now?"

How It's Organized🔗

Content is structured by urgency and depth — the same three tiers as the rest of the Exploring sites.

  • Essentials

    The networking you reach for during an incident — and the mental model underneath it.

    From URL to Endpoint — What "expose an endpoint" really means: DNS, ports, and the bind address that decides who can reach it

    HTTPS for APIs — Where the connection actually gets secured, and why TLS termination changes everything

    DNS debugging, network troubleshooting, load balancers, TLS basics (coming soon)

  • Efficiency

    Design and operate the layer that exposes and secures your services.

    Reverse Proxies and API Gateways — The front door that owns the public address, terminates TLS, and guards your services

    CORS Explained — The browser rule that makes an API "work in curl but fail in the app"

    Certificate management, advanced debugging, Services & Ingress, VPC design (coming soon)

  • Mastery

    Advanced architecture, performance, and scale.

    Service mesh, packet capture and deep troubleshooting, network performance tuning, and multi-region networking (coming soon)

Who This Is For🔗

If you're the person who gets paged when an endpoint goes dark — or the one now asked to expose and secure a new one — this is for you. It assumes you're comfortable in a terminal and want to understand why the network behaves the way it does, not just which command to copy. No traditional networking background required; it meets you where you are.

Part of the Exploring Series🔗

This site is one of an integrated set of learning sites:

  • linux.bradpenney.io — Linux teaches the network commands; this site teaches when and why to use them.
  • k8s.bradpenney.io — Kubernetes teaches Services and Ingress; this site teaches how they actually route traffic.
  • tools.bradpenney.io — the Dev Tools site teaches curl and dig; this site teaches what to send and how to read the response.
  • cs.bradpenney.io — Computer Science covers the theory behind TCP/IP, DNS, and routing.

Getting Started🔗

New here? Start with From URL to Endpoint — once you can see how an endpoint is actually exposed, everything else about securing and debugging it falls into place.