Simplifying SpringBoot Controllers with the @RestController Annotation

The author, a self‑described "architect who writes code and poetry," shares a common frustration among SpringBoot developers: the need to write repetitive configuration and multiple annotations for simple controller tasks.

Typically, creating a REST endpoint requires both @Controller and @ResponseBody , which makes the code verbose. An example of this traditional approach is shown below:

@Controller

@ResponseBody

public class UserController {

    @RequestMapping("/user")

    public User getUser() {

        return new User("张三", 25);
    }
}

To eliminate this redundancy, SpringBoot provides the @RestController annotation, which combines the functionality of @Controller and @ResponseBody . Using it, the same controller can be written more concisely:

@RestController

public class UserController {

    @RequestMapping("/user")

    public User getUser() {

        return new User("张三", 25);
    }
}

This single annotation not only shortens the source code but also embodies SpringBoot's "convention over configuration" philosophy, allowing developers to focus on business logic rather than boilerplate setup.

The author emphasizes that adopting such low‑configuration annotations leads to faster development cycles, clearer architecture, and easier maintenance, especially in large projects like e‑commerce back‑ends where repetitive controller code can become a bottleneck.

In summary, the @RestController annotation is presented as a "smart" shortcut that reduces repetitive configuration, aligns with modern development practices, and improves overall productivity in backend Java development.