Networking and HTTP for Backend Developers
Networking and HTTP for backend developers is how clients and servers communicate. HTTP defines requests with methods, headers and bodies and responses with status codes, DNS resolves names to IP addresses, and proxies and load balancers sit in front of servers to distribute traffic, terminate TLS and hide internal addresses.
Stage: Web and APIs · Part of the Backend Developer roadmap · Last reviewed 19 November 2026
What to learn in Networking and HTTP
- Describe what happens between typing a URL and receiving a page
- Choose the right HTTP method and status code for an operation
- Use curl to send requests with headers and a JSON body
- Explain how DNS resolution works and what a TTL does
- Differentiate a forward proxy, reverse proxy and load balancer
Networking and HTTP interview questions
What is the difference between PUT and PATCH?
PUT replaces a whole resource with the supplied representation and is idempotent. PATCH applies a partial update, sending only the fields that change, and may or may not be idempotent depending on how it is defined. Use PATCH for small edits to avoid overwriting fields.
What does a reverse proxy do?
A reverse proxy such as Nginx receives client requests on behalf of backend servers and forwards them. It can terminate TLS, load balance, cache responses, compress and apply rate limits, while hiding the internal servers from the public internet.
Where Networking and HTTP fits in the Backend Developer roadmap
Networking and HTTP belongs to the Web and APIs stage (beginner level), which takes about 6 hours. HTTP, API design and the architecture of web services.
Other units in this stage
Back to the full Backend Developer roadmap