Embedded server concept in Spring Boot - Step-by-Step Execution

Concept Flow - Embedded server concept

Start Spring Boot Application

↓

Create Embedded Server Instance

↓

Configure Server Settings

↓

Start Server Listening on Port

↓

Handle Incoming HTTP Requests

↓

Process Requests with Controllers

↓

Send HTTP Responses

↓

Application Running with Embedded Server

This flow shows how Spring Boot starts an embedded server, configures it, listens for requests, and processes them within the application.

Execution Sample

Spring Boot

import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;

@SpringBootApplication
public class DemoApplication {
  public static void main(String[] args) {
    SpringApplication.run(DemoApplication.class, args);
  }
}

This code starts a Spring Boot app with an embedded server that listens for HTTP requests.

Execution Table

Step	Action	Result	Server State
1	SpringApplication.run() called	Spring Boot app starts	Server instance created but not started
2	Embedded server (e.g., Tomcat) initialized	Server configured with default port 8080	Server ready to start
3	Server starts listening on port 8080	Server is running and waiting for requests	Server running
4	HTTP request received at /hello	Request passed to controller	Server running, processing request
5	Controller processes request and returns response	Response sent to client	Server running
6	No more requests	Server continues listening	Server running
7	Application stopped	Server shuts down	Server stopped

💡 Application stops or is terminated, embedded server shuts down

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	Final
serverInstance	null	created	running	running	stopped
port	null	8080	8080	8080	null
request	null	null	received	processed	null
response	null	null	null	sent	null

Key Moments - 3 Insights

Why does Spring Boot create an embedded server instead of requiring a separate server?

Spring Boot creates an embedded server automatically (see Step 2 in execution_table) so you don't need to install or configure a separate server. This makes running your app simpler and self-contained.

How does the embedded server handle HTTP requests?

When a request arrives (Step 4), the embedded server passes it to the app's controllers to process and send back a response (Step 5). The server stays running to handle more requests.

What happens if the port 8080 is already in use?

The server will fail to start at Step 3 because it cannot bind to port 8080. You would see an error and need to change the port configuration before restarting.

Visual Quiz - 3 Questions

Look at the execution_table, what is the server state after Step 3?

A Server running and listening on port 8080

B Server created but not started

C Server stopped

D Server processing request

💡 Hint

Check the 'Server State' column for Step 3 in the execution_table

At which step does the embedded server start listening for HTTP requests?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look for the action 'Server starts listening on port 8080' in the execution_table

If the application is stopped, what is the final state of the serverInstance variable?

A null

B created

C stopped

D running

💡 Hint

Check the variable_tracker row for serverInstance at the 'Final' column

Concept Snapshot

Spring Boot Embedded Server Concept:
- Spring Boot auto-creates an embedded server (like Tomcat) inside your app.
- The server starts when you run SpringApplication.run().
- It listens on a default port (8080) for HTTP requests.
- Requests are handled by your controllers inside the app.
- No need to install or configure an external server.
- Server runs until the app stops.

Full Transcript

When you start a Spring Boot application using SpringApplication.run(), it creates an embedded server instance such as Tomcat inside your app. This server is configured automatically and starts listening on port 8080 by default. When an HTTP request arrives, the embedded server passes it to your application's controllers to process and send back a response. The server keeps running and handling requests until the application is stopped, at which point the server shuts down. This embedded server concept means you don't need to install or manage a separate server, making development and deployment simpler and more self-contained.