Understanding Network Ports and Their Role in Web Services

Many developers claim to know TCP/IP but cannot clearly explain what a port is. This article introduces the concept of ports, their typical values, and why they are essential for network communication.

Common Ports

MySQL default port 3306

Redis default port 6379

Tomcat default port 8080

SSH default port 22

Web services mainly use ports 80 (HTTP) and 443 (HTTPS)

When accessing a local service you may type localhost:8080 . In production the port is often omitted because browsers automatically use the protocol’s default port (e.g., https://xiaogd.net implies port 443). If an incorrect port is supplied, the request fails, and a 301 redirect may change the request to the correct default.

HTTP → default port 80 HTTPS → default port 443

Ports are not optional; they allow the operating system to route a request to the correct process among many services (web server, FTP, database, etc.). Without ports the client would need to know the server’s process ID, which is impossible across machines.

Ports act as an indirection layer similar to a naming service: they map a numeric identifier to a running service, just as DNS maps a domain name to an IP address or Spring Cloud Eureka maps a service name to an instance.

This indirection embodies the Inversion of Control (IoC) principle: the client always contacts a well‑known port, while the server decides which process listens on that port.

“Any problem in computer science can be solved with another layer of indirection.” – David Wheeler

For user convenience, default ports hide the numeric details, but developers can configure custom ports (e.g., 9527) if needed, provided the service is listening there and firewalls allow the traffic.

Ports exist for both TCP and UDP; most web traffic uses TCP ports. A TCP packet contains a source port (chosen by the client, e.g., 38672) and a destination port (e.g., 80 or 443). The response returns to the source port, completing the communication.

Understanding ports is fundamental for backend development, network troubleshooting, and designing scalable services.