Why JWT matters for APIs in Spring Boot - Performance Evidence

Performance: Why JWT matters for APIs

MEDIUM IMPACT

This affects API response time and server load by how authentication tokens are verified and managed.

Authenticating API requests efficiently

Spring Boot

Use JWT tokens that carry user info and are verified via signature without DB calls.

No database lookup needed per request, token verified locally by server.

📈 Performance GainReduces authentication latency by 10-50ms per request, improves throughput

Authenticating API requests efficiently

Spring Boot

Use server-side sessions stored in database for every API request authentication check.

Each request triggers a database lookup causing latency and increased server load.

📉 Performance CostBlocks API response for 10-50ms per request depending on DB speed

Performance Comparison

Pattern	DB Calls	CPU Usage	Response Latency	Verdict
Server-side sessions	1 DB call per request	Higher due to DB I/O wait	Increased by 10-50ms	[X] Bad
JWT tokens	No DB calls per request	Lower CPU for signature check	Minimal added latency (~1-2ms)	[OK] Good

Rendering Pipeline

JWT verification happens during API request processing before response generation, affecting server CPU and response time.

→Request Parsing

→Authentication

→Response Generation

⚠️ BottleneckAuthentication stage due to database session lookups in bad pattern

Core Web Vital Affected

INP

This affects API response time and server load by how authentication tokens are verified and managed.

Optimization Tips

1Avoid database lookups on every API request for authentication.

2Use JWT tokens to verify user identity statelessly and locally.

3Faster authentication improves API responsiveness and user experience.

Performance Quiz - 3 Questions

How does using JWT improve API performance compared to server-side sessions?

A By eliminating database lookups for each request

B By caching all user data in memory

C By compressing API responses

D By delaying token verification until after response

DevTools: Network

How to check: Open DevTools Network tab, inspect API request timing, compare response times with and without JWT

What to look for: Look for reduced waiting time on authentication steps and faster overall API response

Practice

1. Why is JWT important for APIs in Spring Boot?

easy

A. It replaces the need for HTTPS in API communication.

B. It stores user passwords in the token for quick access.

C. It securely identifies users without storing session data on the server.

D. It automatically encrypts all API responses.

Solution

1. Step 1: Understand JWT's role in user identification

   JWT carries user identity information inside the token, so the server does not need to keep session data.

2. Step 2: Recognize security benefits

   This stateless approach improves security and scalability by avoiding server-side session storage.

3. Final Answer:

   It securely identifies users without storing session data on the server. -> Option C

4. Quick Check:

   JWT = stateless secure user ID [OK]

Hint: JWT carries user info, no server session needed [OK]

Common Mistakes:

• Thinking JWT stores passwords inside the token
• Believing JWT replaces HTTPS
• Assuming JWT encrypts API responses automatically

2. Which of the following is the correct way to include a JWT in an HTTP request header?

easy

A. Auth-Token: <token>

B. Authorization: Bearer <token>

C. Token: JWT <token>

D. JWT-Authorization: Bearer <token>

Solution

1. Step 1: Recall standard JWT header format

   The standard way to send JWTs is in the Authorization header with the Bearer scheme.

2. Step 2: Match the correct syntax

   "Authorization: Bearer <token>" is the correct and widely accepted format.

3. Final Answer:

   Authorization: Bearer <token> -> Option B

4. Quick Check:

   JWT header = Authorization: Bearer [OK]

Hint: JWT goes in Authorization header with Bearer prefix [OK]

Common Mistakes:

• Using non-standard header names like Token or Auth-Token
• Omitting the Bearer prefix
• Adding extra words like JWT-Authorization

3. Given this Spring Boot controller method snippet, what will happen if the JWT is missing or invalid?

@GetMapping("/profile")
public ResponseEntity<String> getProfile(@RequestHeader("Authorization") String authHeader) {
    if (authHeader == null || !authHeader.startsWith("Bearer ")) {
        return ResponseEntity.status(401).body("Unauthorized");
    }
    String token = authHeader.substring(7);
    // Assume validateToken returns false if token invalid
    if (!jwtService.validateToken(token)) {
        return ResponseEntity.status(401).body("Unauthorized");
    }
    return ResponseEntity.ok("User profile data");
}

medium

A. Returns 500 Internal Server Error on invalid JWT.

B. Returns 200 OK with user profile regardless of JWT.

C. Throws a NullPointerException if JWT is missing.

D. Returns 401 Unauthorized if JWT is missing or invalid.

Solution

1. Step 1: Check handling of missing or malformed Authorization header

   The code returns 401 Unauthorized if the header is missing or does not start with "Bearer ".

2. Step 2: Check token validation logic

   If the token is invalid, the method also returns 401 Unauthorized.

3. Final Answer:

   Returns 401 Unauthorized if JWT is missing or invalid. -> Option D

4. Quick Check:

   Missing/invalid JWT = 401 Unauthorized [OK]

Hint: Missing or bad JWT triggers 401 Unauthorized [OK]

Common Mistakes:

• Assuming it returns 200 OK without JWT
• Expecting exceptions instead of 401 response
• Thinking it returns 500 error on invalid token

4. Identify the bug in this Spring Boot JWT filter snippet:

public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
    HttpServletRequest req = (HttpServletRequest) request;
    String authHeader = req.getHeader("Authorization");
    if (authHeader != null && authHeader.startsWith("Bearer ")) {
        String token = authHeader.substring(7);
        if (jwtService.validateToken(token)) {
            SecurityContextHolder.getContext().setAuthentication(null);
        }
    }
    chain.doFilter(request, response);
}

medium

A. It sets authentication to null instead of a valid Authentication object.

B. It does not check if authHeader is null before substring.

C. It calls chain.doFilter before validating the token.

D. It uses the wrong header name for JWT.

Solution

1. Step 1: Analyze authentication setting logic

   The code sets authentication to null even when the token is valid, which means no user is authenticated.

2. Step 2: Understand correct behavior

   It should set a valid Authentication object to represent the logged-in user, not null.

3. Final Answer:

   It sets authentication to null instead of a valid Authentication object. -> Option A

4. Quick Check:

   Valid token must set Authentication, not null [OK]

Hint: Valid token must set Authentication object, not null [OK]

Common Mistakes:

• Ignoring that authentication is set to null
• Thinking substring without null check causes error here
• Assuming chain.doFilter order is wrong
• Believing header name is incorrect

5. You want your Spring Boot API to allow users to stay logged in without server sessions, using JWT. Which approach best achieves this while keeping the API stateless and secure?

hard

A. Generate a JWT after login containing user info, send it to client, and require it in Authorization header for each request.

B. Store user sessions in a database and send session IDs in cookies to clients.

C. Send user credentials with every API request and validate each time on the server.

D. Use JWT only for login, then switch to server sessions for other requests.

Solution

1. Step 1: Understand stateless authentication with JWT

   JWT tokens carry user info and are sent by clients with each request, so the server does not store session data.

2. Step 2: Compare with other methods

   Storing sessions or sending credentials every time breaks statelessness or security best practices.

3. Final Answer:

   Generate a JWT after login containing user info, send it to client, and require it in Authorization header for each request. -> Option A

4. Quick Check:

   JWT = stateless secure token per request [OK]

Hint: JWT tokens keep API stateless and secure per request [OK]

Common Mistakes:

• Using server sessions instead of JWT for statelessness
• Sending credentials on every request
• Switching between JWT and sessions inconsistently