Networking for DevOps Engineers
Networking for DevOps is the understanding of how traffic moves between services. It covers TCP and IP addressing, subnets, ports, DNS resolution and HTTP and TLS, plus load balancers and reverse proxies that spread and route requests. Most deployment and outage problems involve a network layer somewhere.
Stage: Networking · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Networking
- Explain the TCP three-way handshake and what a port is
- Calculate a subnet range from a CIDR block
- Trace DNS resolution for a domain with dig
- Debug an HTTP request with curl -v and read status codes
- Compare layer 4 and layer 7 load balancing
- Configure a reverse proxy with health checks
Networking interview questions
How does a browser reach your service through DNS and a load balancer?
The browser resolves the domain through DNS to an IP address, opens a TCP connection, performs a TLS handshake for HTTPS, sends an HTTP request, receives the response and renders it. Caches and load balancers may be involved at several steps. A load balancer or reverse proxy usually answers for the service.
What is the difference between a layer 4 and a layer 7 load balancer?
A layer 4 balancer routes by IP address and port without reading the content, so it is fast and protocol-agnostic. A layer 7 balancer understands HTTP and can route by host, path or header, terminate TLS and apply rules.
Where Networking fits in the DevOps Engineer roadmap
Networking belongs to the Networking stage (intermediate level). How machines talk: TCP/IP, DNS, HTTP and load balancing.
Back to the full DevOps Engineer roadmap