@ControllerAdvice for global handling in Spring Boot - Performance & Optimization

Performance: @ControllerAdvice for global handling

MEDIUM IMPACT

This affects server response time and error handling efficiency, impacting how fast and smoothly error responses are generated and sent to the client.

Handling exceptions globally in a Spring Boot application

Spring Boot

@ControllerAdvice
public class GlobalExceptionHandler {
  @ExceptionHandler(UserNotFoundException.class)
  public ResponseEntity<String> handleUserNotFound(UserNotFoundException ex) {
    return ResponseEntity.status(HttpStatus.NOT_FOUND).body(ex.getMessage());
  }
}

@RestController
public class UserController {
  @GetMapping("/user/{id}")
  public User getUser(@PathVariable String id) {
    // fetch user without try-catch
  }
}

Centralizes exception handling, reducing duplicate code and improving maintainability. The server handles exceptions once per type, improving response consistency.

📈 Performance GainReduces CPU cycles spent on repeated try-catch blocks, slightly improving throughput and reducing response time under load.

Handling exceptions globally in a Spring Boot application

Spring Boot

@RestController
public class UserController {
  @GetMapping("/user/{id}")
  public ResponseEntity<User> getUser(@PathVariable String id) {
    try {
      // fetch user
    } catch (UserNotFoundException e) {
      return ResponseEntity.status(HttpStatus.NOT_FOUND).body(null);
    }
    return ResponseEntity.ok(user);
  }
  // similar try-catch in every controller method
}

Duplicating try-catch blocks in every controller method increases code size and maintenance cost, and can slow down request processing due to repeated exception handling logic.

📉 Performance CostAdds redundant exception handling code in every controller, increasing CPU usage and response time slightly under load.

Performance Comparison

Pattern	Code Duplication	CPU Usage	Response Time Impact	Verdict
Try-catch in every controller method	High	Higher due to repeated handling	Slightly slower under load	[X] Bad
Centralized @ControllerAdvice handling	Low	Lower due to single handling point	Faster and more consistent	[OK] Good

Rendering Pipeline

When an exception occurs, Spring routes it to the @ControllerAdvice handler before sending the response. This avoids repeated exception handling logic in controllers and streamlines error response generation.

→Request Handling

→Exception Resolution

→Response Generation

⚠️ BottleneckException Resolution stage can be costly if duplicated in many controllers.

Optimization Tips

1Centralize exception handling with @ControllerAdvice to reduce duplicate code.

2Avoid try-catch blocks in every controller method to save CPU cycles.

3Monitor server logs and response times to verify efficient error handling.

Performance Quiz - 3 Questions

What is a main performance benefit of using @ControllerAdvice for exception handling?

A Delays response by adding extra processing steps

B Reduces duplicate exception handling code and CPU usage

C Increases bundle size by adding more classes

D Improves client-side rendering speed

DevTools: Spring Boot Actuator and Application Logs

How to check: Enable actuator endpoints and monitor logs for exception handling frequency and response times. Use profiling tools to measure CPU usage during error scenarios.

What to look for: Look for reduced duplicate exception logs and faster error response times indicating centralized handling.