Request Mapping

🔍 What Is It?

@RequestMapping in Spring Boot is the annotation-based routing system that tells Spring Boot which controller method should handle a specific HTTP request. When developers search for @RequestMapping in Spring Boot, they usually want to understand how path patterns, HTTP methods, and controller design work together.

Quick Facts

• →Used in: REST controllers, web MVC endpoints, versioned APIs, and content-type specific handlers
• →Best for: Building clear controller routes with explicit HTTP method behavior
• →Interview importance: High because request mapping is a common Spring Boot interview topic
• →Production relevance: High because API contracts, routing safety, and handler clarity depend on it
• →Related topics: Controllers, path variables, request params, exception handling
• →Last updated: July 2026

Mapping annotations

• →@RequestMapping(path, method, consumes, produces, headers, params) - most flexible
• →@GetMapping - shorthand for @RequestMapping(method=GET)
• →@PostMapping - shorthand for @RequestMapping(method=POST)
• →@PutMapping - shorthand for @RequestMapping(method=PUT)
• →@DeleteMapping - shorthand for @RequestMapping(method=DELETE)
• →@PatchMapping - shorthand for @RequestMapping(method=PATCH)

Mapping options

• →Path: /users, /users/{id}, /users/**
• →Method: GET, POST, PUT, DELETE, PATCH
• →Consumes: application/json, multipart/form-data
• →Produces: application/json, application/xml
• →Headers: require specific request headers
• →Params: require specific query parameters

🎯 Why Do We Need It?

Request mapping provides the routing contract for your Spring Boot API. Without it, there is no clear way to connect an HTTP request to the controller method that should validate input, call business logic, and shape the response.

Interview Relevance

• →Interviewers ask request mapping to test whether you understand controller design, REST conventions, and handler selection
• →Strong answers explain class-level versus method-level mappings, path variables, consumes or produces rules, and shortcut annotations
• →Senior discussions often move into ambiguous mappings, API versioning, validation, and public contract stability

🏗️ What Happens in Real Projects?

Production Usage

Every REST API endpoint is defined by a combination of HTTP method + URL path:

• →GET /api/v1/users - list users
• →GET /api/v1/users/{id} - get user by ID
• →POST /api/v1/users - create user
• →PUT /api/v1/users/{id} - replace user
• →PATCH /api/v1/users/{id} - partial update
• →DELETE /api/v1/users/{id} - delete user

Production teams also use request mapping to control media types, route versioning, nested resources, and backward-compatible endpoint evolution across multiple clients.

⚙️ How It Works

Spring's DispatcherServlet receives every HTTP request. It consults the HandlerMapping built from your @RequestMapping annotations to find the matching controller method. If multiple methods match, Spring uses specificity rules to pick the best match. If no match is found, 404 is returned.

@RequestMapping vs @GetMapping

• →@RequestMapping is the flexible base annotation for path, method, headers, params, consumes, and produces
• →@GetMapping, @PostMapping, @PutMapping, and the others are shortcuts that make REST controller methods easier to scan quickly

💻 Example

Request Mapping Patterns — Common mapping patterns used in enterprise REST APIs.

@RestController
@RequestMapping("/api/v1/products")  // Base path for all methods
public class ProductController {

    @GetMapping                          // GET /api/v1/products
    public Page<ProductDto> list(@RequestParam(defaultValue="0") int page) { ... }

    @GetMapping("/{id}")                 // GET /api/v1/products/42
    public ProductDto getById(@PathVariable Long id) { ... }

    @PostMapping                         // POST /api/v1/products
    @ResponseStatus(HttpStatus.CREATED)
    public ProductDto create(@Valid @RequestBody CreateProductRequest req) { ... }

    @PutMapping("/{id}")                 // PUT /api/v1/products/42
    public ProductDto replace(@PathVariable Long id,
                               @Valid @RequestBody UpdateProductRequest req) { ... }

    @PatchMapping("/{id}")
    public ProductDto partialUpdate(@PathVariable Long id,
                                     @RequestBody Map<String, Object> updates) { ... }

    @DeleteMapping("/{id}")
    @ResponseStatus(HttpStatus.NO_CONTENT)
    public void delete(@PathVariable Long id) { ... }

    // Nested resource: GET /api/v1/products/42/reviews
    @GetMapping("/{id}/reviews")
    public List<ReviewDto> getReviews(@PathVariable Long id) { ... }
}

🤔 Common Confusions

🚨 Common Production Issues

✅ Best Practices

🏛️ Architect's Note

💬 Frequently Asked Questions

🎯 Key Takeaways

🔗 Related Topics

🎯 Practice this topic in interviews

↗ Where this topic fits