0 of 3 done
The network layer a DevOps engineer must actually understand: the protocols underneath everything (DNS, HTTP/S, TLS, SSH, the OSI model), and the web-serving infrastructure that sits in front of applications (Nginx, reverse proxies, load balancers, caching). Part of the DevOps curriculum.
This section overlaps the foundations/networking/ domain (currently empty) — this is the operational cut (running and debugging network services), not the CS-theory cut. If that domain gets built out later, the OSI/TCP theory belongs there and this section should cross-link to it.
Reading order
- Networking & Protocols — [Intermediate] — the OSI model, TCP/UDP, DNS, HTTP/HTTPS, SSL/TLS, SSH, ports, and the email protocols (SMTP/IMAP/POP3, SPF/DKIM/DMARC)
- Web Servers & Proxies — [Intermediate] — Nginx in depth, Apache/Caddy, forward vs reverse proxy, load balancing, and caching servers
- Local HTTPS Tunnels — [Intermediate] — exposing localhost over public HTTPS for OAuth callbacks and webhooks; cloudflared vs ngrok, named vs quick tunnels
Related
- Linux networking fundamentals — the host-level view
- SSH config — SSH in practice
- Secret Management — TLS certificates are secrets
- DevOps curriculum map
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering