What is the difference between @Controller and @RestController?
PICTURE THIS: A REST CALL
Simple meaning
@Controller is for MVC that returns view names
WHY — Spring Boot instead of guessing?
Why interviewers care about Spring Boot:
contrast on Spring Boot, not two memorised paragraphs.
the developer, then one case where picking wrong hurts.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1@Controller is for MVC
that returns view names
- 2you need @ResponseBody on
methods that return JSON.
- 3@RestController is @Controller plus
@ResponseBody on every method, which is what REST APIs want.
- 4For a JSON backend
interview, @RestController is the expected default.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
@Controller is for MVC that returns view names you need @ResponseBody on methods that return JSON.