Why Do Web Services Need Ports? Uncovering the Hidden Layer of Network Communication

Common Ports

In everyday development, especially for backend developers, you encounter many well‑known ports: MySQL uses 3306, Redis 6379, Tomcat 8080, SSH 22, and the most important web ports 80 (HTTP) and 443 (HTTPS).

Are Ports Necessary?

During local web development you often access localhost:8080. When the site is deployed, the port seems to disappear because browsers use default ports: 80 for HTTP and 443 for HTTPS. For example, https://xiaogd.net actually uses port 443.

You can see the default port in Chrome's developer tools.

If you manually specify a wrong port, such as https://xiaogd.net:80, the request fails; changing the scheme to HTTP makes it work because the server redirects HTTP to HTTPS (301). Conversely, http://xiaogd.net:443 also fails.

Default Ports of Protocols

HTTP → port 80

HTTPS → port 443

If you enter an arbitrary port like 9527, the request fails unless a service is listening on that port.

Why Ports Are Needed

Ports act as an indirection layer that maps a network address (IP) to a specific process. Without ports, the operating system would not know which process should handle an incoming request.

Inter‑Process Communication (IPC)

When you type a domain name, DNS resolves it to an IP address, but many processes may be running on that host (web server, FTP, database, etc.). The client must specify both the IP and a port so the server can route the request to the correct process.

Ports as an Indirection Layer

Clients cannot know the server's process ID, and process IDs can change after a restart. Ports provide a stable, abstract identifier that decouples clients from server implementation details.

Any computer problem can be solved by adding another layer of indirection – but that layer may introduce new complexity.

With ports, the client always contacts a well‑known port (80 or 443); the server adapts by listening on that port, reversing the dependency.

Real‑World Analogy

Think of a government service center: each window number (e.g., window 80) handles a specific type of request. Citizens go to the window without needing to know which staff member is behind it.

Ports as a Naming Service

Just like DNS maps a domain name to an IP, a port maps a service name (e.g., "web") to a numeric identifier. Frameworks such as Spring Cloud Eureka use similar concepts.

Ports and Inversion of Control (IoC)

By exposing a fixed port, the server allows the client to dictate where to send requests, effectively inverting control: the client controls the entry point, and the server binds to that port.

TCP vs. UDP Ports

Ports exist for both TCP and UDP. Most web traffic uses TCP ports 80 and 443; UDP ports with the same numbers are distinct and rarely used for HTTP.

When a TCP connection is established, the client picks a random source port (e.g., 38672) and the server responds to that port, completing the bidirectional communication.

Further details about sockets, virtual hosts, reverse proxies, etc., are omitted for brevity.