@RestController annotation in Spring Boot - Performance & Optimization

Performance: @RestController annotation

MEDIUM IMPACT

This affects server response time and client perceived load speed by simplifying REST API endpoint creation.

Creating REST API endpoints in Spring Boot

Spring Boot

@RestController
public class MyController {
  @RequestMapping("/data")
  public String getData() {
    return "Hello";
  }
}

Combines @Controller and @ResponseBody, reducing annotation overhead and ensuring consistent JSON or text responses.

📈 Performance GainReduces server processing steps, improving response time and lowering LCP.

Creating REST API endpoints in Spring Boot

Spring Boot

@Controller
public class MyController {
  @RequestMapping("/data")
  @ResponseBody
  public String getData() {
    return "Hello";
  }
}

Separately using @Controller and @ResponseBody adds boilerplate and can lead to inconsistent response handling.

📉 Performance CostSlightly increased server processing due to extra annotation handling and potential misconfiguration.

Performance Comparison

Pattern	Server Processing	Annotation Overhead	Response Consistency	Verdict
@Controller + @ResponseBody	Moderate	Higher due to multiple annotations	Consistent if used correctly	[!] OK
@RestController	Lower	Minimal, combined annotation	Always consistent JSON/text response	[OK] Good

Rendering Pipeline

The @RestController annotation affects the server-side processing before the browser rendering pipeline starts. It streamlines response generation, reducing server response time which impacts the browser's Largest Contentful Paint (LCP).

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing stage due to response serialization and annotation handling

Core Web Vital Affected

LCP

This affects server response time and client perceived load speed by simplifying REST API endpoint creation.

Optimization Tips

1Use @RestController to combine @Controller and @ResponseBody for faster server responses.

2Reducing server annotation overhead improves LCP by speeding up content delivery.

3Consistent JSON or text responses from @RestController avoid extra processing delays.

Performance Quiz - 3 Questions

How does using @RestController improve performance compared to @Controller with @ResponseBody?

A It combines annotations to reduce server processing overhead.

B It caches responses automatically to speed up loading.

C It compresses the response payload to reduce size.

D It delays response until all data is fully processed.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the API endpoint, and check the response time and payload size.

What to look for: Look for faster response times and consistent JSON or text responses indicating efficient server processing.

Practice

1. What is the main purpose of the @RestController annotation in Spring Boot?

easy

A. To create HTML views for web pages

B. To define a service class for business logic

C. To create a controller that returns data directly as JSON or XML

D. To configure database connections

Solution

1. Step 1: Understand the role of @RestController

   @RestController is used to create REST APIs that return data directly, usually in JSON or XML format.

2. Step 2: Compare with other options

   Creating HTML views is handled by MVC controllers, defining service classes by @Service, and configuring database connections elsewhere in Spring Boot.

3. Final Answer:

   To create a controller that returns data directly as JSON or XML -> Option C

4. Quick Check:

   @RestController = returns data directly [OK]

Hint: Remember: @RestController returns data, not HTML pages [OK]

Common Mistakes:

• Confusing @RestController with @Service
• Thinking it renders HTML views
• Assuming it configures database

2. Which of the following is the correct way to declare a Spring Boot REST controller?

easy

A. @Service public class MyController {}

B. @Controller public class MyController {}

C. @RestService public class MyController {}

D. @RestController public class MyController {}

Solution

1. Step 1: Identify the correct annotation for REST controllers

   @RestController is the correct annotation to create REST APIs in Spring Boot.

2. Step 2: Check other annotations

   @Controller is for MVC controllers returning views, @RestService is not a valid annotation, and @Service is for service classes.

3. Final Answer:

   @RestController public class MyController {} -> Option D

4. Quick Check:

   Correct REST controller syntax = @RestController public class MyController {} [OK]

Hint: Use @RestController for REST APIs, not @Controller [OK]

Common Mistakes:

• Using @Controller instead of @RestController
• Using non-existent @RestService annotation
• Confusing @Service with controller annotations

3. Given the following code, what will be the output when accessing /hello endpoint?

@RestController
public class HelloController {
    @GetMapping("/hello")
    public String sayHello() {
        return "Hello, Spring!";
    }
}

medium

A. An HTML page displaying "Hello, Spring!"

B. A plain text response with the string "Hello, Spring!"

C. A 404 Not Found error

D. A compilation error due to missing annotations

Solution

1. Step 1: Understand @RestController behavior

   @RestController returns the method's return value directly as the response body, usually JSON or plain text.

2. Step 2: Analyze the method return

   The method returns a String "Hello, Spring!" which will be sent as plain text in the response body.

3. Final Answer:

   A plain text response with the string "Hello, Spring!" -> Option B

4. Quick Check:

   @RestController + String return = plain text response [OK]

Hint: @RestController returns method data as response body [OK]

Common Mistakes:

• Expecting an HTML page instead of data
• Thinking it causes 404 without mapping
• Assuming compilation error without reason

4. Identify the error in this Spring Boot REST controller code:

@RestController
public class UserController {
    @GetMapping("/user")
    public User getUser() {
        User user = new User();
        user.setName("Alice");
        return user;
    }
}

Assume User is a simple POJO with a name field and getters/setters.

medium

A. No error; code will return User object as JSON

B. User class must be annotated with @Entity

C. Missing @ResponseBody annotation on getUser() method

D. Missing @RequestMapping on class level

Solution

1. Step 1: Check @RestController effect

   @RestController automatically adds @ResponseBody to all methods, so no need to add it explicitly.

2. Step 2: Verify User class requirements

   User is a POJO; it does not need @Entity unless used with database. Returning it will serialize to JSON automatically.

3. Final Answer:

   No error; code will return User object as JSON -> Option A

4. Quick Check:

   @RestController auto @ResponseBody = No error; code will return User object as JSON [OK]

Hint: @RestController adds @ResponseBody automatically [OK]

Common Mistakes:

• Adding unnecessary @ResponseBody on methods
• Confusing @Entity with serialization
• Thinking class-level @RequestMapping is mandatory

5. You want to create a REST API that returns a list of users as JSON. Which of the following code snippets correctly uses @RestController to achieve this?

hard

A. @RestController
public class UserApi {
@GetMapping("/users")
public List<String> getUsers() {
return List.of("Alice", "Bob", "Carol");
}
}

B. @RestController
public class UserApi {
@GetMapping("/users")
public String getUsers() {
return "Alice, Bob, Carol";
}
}

C. @Controller
public class UserApi {
@GetMapping("/users")
public List<String> getUsers() {
return List.of("Alice", "Bob", "Carol");
}
}

D. @RestController
public class UserApi {
@RequestMapping("/users")
public void getUsers() {
System.out.println("Alice, Bob, Carol");
}
}

Solution

1. Step 1: Check @RestController and return type

   @RestController public class UserApi { @GetMapping("/users") public List<String> getUsers() { return List.of("Alice", "Bob", "Carol"); } } uses @RestController and returns a List<String>, which Spring Boot converts to JSON automatically.

2. Step 2: Analyze other options

   The snippet returning String sends a plain string, not a JSON list. The snippet using @Controller attempts to resolve a view name, not return JSON data. The snippet with void return type sends no response body, only prints to console.

3. Final Answer:

   @RestController public class UserApi { @GetMapping("/users") public List<String> getUsers() { return List.of("Alice", "Bob", "Carol"); } } -> Option A

4. Quick Check:

   @RestController + List return = JSON list [OK]

Hint: Return List with @RestController for JSON array response [OK]

Common Mistakes:

• Using @Controller instead of @RestController for JSON
• Returning void or printing instead of returning data
• Returning plain string instead of list for JSON array