How Web Containers Stay Alive: Inside Java Servlets, Netty, and Sockets

In Java web applications, a container is the runtime environment that manages and runs components such as Servlets, handling HTTP requests from clients and returning responses.

Main Function

Java classes have a main entry point that runs once and then exits. Unlike a simple while(true) loop, a web server must stay alive to continuously accept requests. It does this by using a socket server that listens on a port, blocks threads, and processes incoming I/O events.

The container’s core is a SocketServer that listens for connections. When a request arrives, the server remains in a listening state instead of terminating, waiting for events such as HTTP requests.

Thus the essential functions of a web container are to handle I/O (socket I/O) and to manage a thread pool for processing each connection. Any framework capable of handling I/O can serve as a web container; the web server is essentially an I/O‑handling server for protocols like HTTP, WebSocket, TCP, UDP, or custom protocols.

Servlet

Servlets are the foundation of Java web development. The container creates a connection, assigns a thread, and routes the request to the appropriate Servlet, which then generates a response. Modern Spring Boot applications embed a container, and Spring MVC wraps Servlets, allowing developers to define controllers with annotations such as @RequestMapping or @PostMapping without manually configuring Servlet mappings.

Netty

The core capability of a web container is socket port listening. Netty is an NIO‑based networking framework that can handle HTTP and custom protocols using an event‑driven model, making it suitable for high‑concurrency servers. Spring WebFlux builds on Netty, providing a reactive web server that outperforms traditional Servlet containers like Tomcat.

Business Gateway

Gateway layers need request forwarding, load balancing, and high concurrency, so they are often built with WebFlux. Unlike Nginx, which only forwards traffic, a WebFlux‑based gateway can embed business logic, rate limiting, circuit breaking, and authentication, offering both routing and code execution capabilities.