ໃນເວລາທີ່ພວກເຮົາມີການອອກແບບໃຫມ່ຂອງບໍລິສັດ, ພວກເຮົາມີຄວາມຮູ້ສຶກວ່າສິ່ງທີ່ສໍາຄັນທີ່ເຮັດໃຫ້ລູກຄ້າບໍ່ມີຄວາມສຸກແມ່ນບໍ່ແມ່ນຜົນປະໂຫຍດຫຼືອິນເຕີເນັດຂອງຜູ້ໃຊ້; ມັນແມ່ນບັນຫາທີ່ບໍ່ໄດ້ຮັບການປິ່ນປົວທີ່ເຄື່ອນໄຫວການປິ່ນປົວ. ໃນ Spring Boot ຫຼືຮູບແບບທີ່ແຕກຕ່າງກັນໃນ frameworks ອື່ນໆ, ກະລຸນາຮັບປະກັນວ່າລະບົບປະຕິບັດຕາມການຄາດຄະເນດຽວກັນໃນເວລາທີ່ພວກເຂົາເຈົ້າແມ່ນຢູ່ໃນຄວາມກົດດັນ. ການຄາດຄະເນດຽວກັນກັບຄໍາແນະນໍາການຄາດຄະເນດິນດີຕ້ອນຮັບ: ການຄາດຄະເນດິນດີຕ້ອນຮັບກ່ອນທີ່ມັນເກີດຂຶ້ນ. @ControllerAdvice Why This Matters ໃນເວລາທີ່ທ່ານສ້າງ REST APIs ໃນ ຂໍຂອບໃຈວ່າທ່ານຈະຕອບສະຫນອງຄວາມປອດໄພຂອງພວກເຮົາ: Spring Boot “ ” How do I handle errors neatly without writing repetitive try-catch blocks everywhere? ຊື່ຫຍໍ້ຂອງ : Have ທຸກຄົນອາດຈະບໍ່ໄດ້ເຮັດວຽກກັບ A ການເຂົ້າລະຫັດທີ່ບໍ່ມີຄຸນນະສົມບັດ, ຫຼືຄຸນນະສົມບັດທີ່ບໍ່ມີ. ໃນຂະນະທີ່ທ່ານຕ້ອງການທີ່ຈະຊອກຫາ tracks stack, ທ່ານຕ້ອງການ . 50+ endpoints ລະຫັດ QR consistent, meaningful, and client-friendly error responses ນີ້ແມ່ນທີ່ ປະຕິບັດຕາມ - ມັນ centralizes ການປິ່ນປົວຜົນກະທົບທັງຫມົດໃນຫນຶ່ງສະຖານທີ່. ດາວນ໌ໂຫລດ ການກໍ່ສ້າງນີ້ step by step, ມີຕົວຢ່າງໃນໂລກທີ່ແທ້ຈິງ. @ControllerAdvice how Use Case — User Management REST API ພວກເຮົາຈະສ້າງ A ມັນສະຫນັບສະຫນູນ: simple User API 
 
 
 
 
 
 Fetching users 
 
 Creating users 
 
 
 Simulating failures for testing Our goal → build a   that returns clean JSON responses. unified global error-handling layer Step 1: Project Setup Dependencies (Maven): <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-web</artifactId>
    </dependency>
    
    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-starter-validation</artifactId>
    </dependency>
 This brings in web + validation support. Then create your main app: @SpringBootApplication
public class ExceptionHandlerDemoApplication {
    public static void main(String[] args) {
        SpringApplication.run(ExceptionHandlerDemoApplication.class, args);
    }
}
 Step 2: Define the Entity — User.java @Data
@AllArgsConstructor
@NoArgsConstructor
public class User {
    private int id;
    @NotBlank(message = "Name cannot be blank")
    private String name;
    @Min(value = 18, message = "Age must be at least 18")
    private int age;
}
 ເປັນຫຍັງ: **We add simple validations so Spring can trigger Method Argument Not Valid Exception automatically when input is invalid. Step 3: Custom Exception for Missing Data public class ResourceNotFoundException extends RuntimeException {
    public ResourceNotFoundException(String message) {
        super(message);
    }
}
public class InvalidRequestException extends RuntimeException {
    public InvalidRequestException(String message) {
        super(message);
    }
}
 ເປັນຫຍັງ: ** ເພື່ອສະຫນັບສະຫນູນຄວາມເປັນສ່ວນຕົວຂອງ "ຜູ້ໃຊ້ທີ່ບໍ່ໄດ້ຮັບການຊອກຫາ" ໃນຂະນະທີ່ບໍ່ມີອະນຸຍາດທົ່ວໄປ. Step 4: Build the Controller @RestController
@RequestMapping("/api/users")
public class UserController {
    // Simple GET that throws ResourceNotFoundException for id > 100
    @GetMapping("/{id}")
    public String getUser(@PathVariable("id") @Min(1) Integer id) {
        if (id > 100) {
            throw new ResourceNotFoundException("User with id " + id + " not found");
        }
        return "User-" + id;
    }
    // Create user example to demonstrate validation
    public static record CreateUserRequest(
            @NotBlank(message = "name is required") String name,
            @Min(value = 18, message = "age must be >= 18") int age) {}
    @PostMapping
    @ResponseStatus(HttpStatus.CREATED)
    public String createUser(@RequestBody @Valid CreateUserRequest body) {
        if ("bad".equalsIgnoreCase(body.name())) {
            throw new InvalidRequestException("Name 'bad' is not allowed");
        }
        return "created:" + body.name();
    }
    // Endpoint to force a server error for demo
    @GetMapping("/boom")
    public void boom() {
        throw new IllegalStateException("simulated server error");
    }
}
 ເປັນຫຍັງ: ** ພວກເຮົາສ້າງສະຖາບັນທີ່ແທ້ຈິງ - ບໍ່ໄດ້ຊອກຫາ, errors validation, ແລະ errors runtime - ທີ່ຜູ້ຈັດການທົ່ວໂລກຂອງພວກເຮົາຈະຄຸ້ມຄອງ. Step 5: Create a Standard Error Model @Data
@AllArgsConstructor
@NoArgsConstructor
public class ErrorResponse {
    private OffsetDateTime timestamp;
    private int status;
    private String error;
    private String message;
    private String path;
    private List<FieldError> fieldErrors;}
 ເປັນຫຍັງ: ** APIs ທັງຫມົດຈໍາເປັນຕ້ອງຂຽນຄວາມຜິດພາດໃນຄອບຄົວທີ່ແຕກຕ່າງກັນ - ນີ້ປັບປຸງການຄວບຄຸມແລະ debug ໃນການຜະລິດ. Step 6: Implement @ControllerAdvice (Global Handler) @ControllerAdvice
public class GlobalExceptionHandler {
    private final Logger log = LoggerFactory.getLogger(GlobalExceptionHandler.class);
    // Handle custom validation exceptions
    @ExceptionHandler(InvalidRequestException.class)
    public ResponseEntity<ErrorResponse> handleInvalidRequest(InvalidRequestException ex, HttpServletRequest req) {
        log.debug("InvalidRequestException: {}", ex.getMessage());
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.BAD_REQUEST.value(),
                HttpStatus.BAD_REQUEST.getReasonPhrase(), ex.getMessage(), req.getRequestURI());
        return ResponseEntity.status(HttpStatus.BAD_REQUEST).body(body);
    }
    // Resource not found -> 404
    @ExceptionHandler(ResourceNotFoundException.class)
    public ResponseEntity<ErrorResponse> handleNotFound(ResourceNotFoundException ex, HttpServletRequest req) {
        log.debug("ResourceNotFoundException: {}", ex.getMessage());
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.NOT_FOUND.value(),
                HttpStatus.NOT_FOUND.getReasonPhrase(), ex.getMessage(), req.getRequestURI());
        return ResponseEntity.status(HttpStatus.NOT_FOUND).body(body);
    }
    // Validation errors from @Valid on request bodies
    @ExceptionHandler(MethodArgumentNotValidException.class)
    public ResponseEntity<ErrorResponse> handleValidation(MethodArgumentNotValidException ex, HttpServletRequest req) {
        log.debug("Validation failed: {}", ex.getMessage());
        List<ErrorResponse.FieldError> fieldErrors = ex.getBindingResult().getFieldErrors().stream()
                .map(fe -> new ErrorResponse.FieldError(fe.getField(), fe.getRejectedValue(), fe.getDefaultMessage()))
                .collect(Collectors.toList());
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.BAD_REQUEST.value(),
                HttpStatus.BAD_REQUEST.getReasonPhrase(), "Validation failed", req.getRequestURI());
        body.setFieldErrors(fieldErrors);
        return ResponseEntity.badRequest().body(body);
    }
    // Type mismatch for method args (?id=abc)
    @ExceptionHandler(MethodArgumentTypeMismatchException.class)
    public ResponseEntity<ErrorResponse> handleTypeMismatch(MethodArgumentTypeMismatchException ex, HttpServletRequest req) {
        log.debug("Type mismatch: {}", ex.getMessage());
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.BAD_REQUEST.value(),
                HttpStatus.BAD_REQUEST.getReasonPhrase(), ex.getMessage(), req.getRequestURI());
        return ResponseEntity.badRequest().body(body);
    }
    // No handler found (404 for unmatched endpoints)
    @ExceptionHandler(NoHandlerFoundException.class)
    public ResponseEntity<ErrorResponse> handleNoHandler(NoHandlerFoundException ex, HttpServletRequest req) {
        log.debug("NoHandlerFound: {} {}", ex.getHttpMethod(), ex.getRequestURL());
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.NOT_FOUND.value(),
                HttpStatus.NOT_FOUND.getReasonPhrase(), "Endpoint not found", req.getRequestURL().toString());
        return ResponseEntity.status(HttpStatus.NOT_FOUND).body(body);
    }
    // Generic fallback
    @ExceptionHandler(Exception.class)
    public ResponseEntity<ErrorResponse> handleAll(Exception ex, HttpServletRequest req) {
        log.error("Unhandled exception: ", ex);
        ErrorResponse body = new ErrorResponse(OffsetDateTime.now(), HttpStatus.INTERNAL_SERVER_ERROR.value(),
                HttpStatus.INTERNAL_SERVER_ERROR.getReasonPhrase(), "An internal error occurred", req.getRequestURI());
        return ResponseEntity.status(HttpStatus.INTERNAL_SERVER_ERROR).body(body);
    }
}
 Why: 
 
 
 
 @ControllerAdvice → ເຮັດໃຫ້ມັນທົ່ວໂລກໃນໄລຍະການຄວບຄຸມທັງຫມົດ. @ExceptionHandler → captures ປະເພດທີ່ແຕກຕ່າງກັນ. ການຊ່ວຍເຫຼືອ buildResponse() ເຮັດໃຫ້ລະຫັດ DRY ແລະ clean. Step 7: Test Scenarios   GET /api/users/1 ລະຫັດການຕອບ: 200 -Success ປະເພດ ປະເພດ GET /api/users/999 ລະຫັດການຕອບ: 404 Resource Not Found ປະເພດ ປະເພດ Validation Error ຊື່ຫຍໍ້ຂອງ : POST / API / users {"name":"", "age": 15} Response: ປະເພດ ປະເພດ Unexpected Error ຊື່ຫຍໍ້ຂອງ : GET /api/user/boom ປະເພດ ປະເພດ Why This Approach Works in Real Projects 
 
 
 
 
 
 
 
 
 
 Problem 
 Solution 
 
 
 
 Too many try-catch blocks 
 Centralized handling with @ControllerAdvice 
 
 
 
 Inconsistent responses 
 Unified ErrorResponse structure 
 
 
 
 Hard to debug 
 Standardized messages with timestamps and paths 
 
 
 
 Client confusion 
 Clear, meaningful messages for each failure type ຜະລິດຕະພັນ ການປິ່ນປົວທີ່ສູນກາງທີ່ມີ @ControllerAdvice ຄໍາຖາມ Inconsistent ການກໍ່ສ້າງ ErrorResponse Unified ດາວນ໌ໂຫລດ Debug ສະ ຫນັບ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ສະ ຫນູນ ຄູ່ມື Customer Confusion ຄໍາຮ້ອງສະຫມັກທີ່ເຂັ້ມແຂງແລະມີຄຸນນະສົມບັດສໍາລັບທຸກປະເພດຂອງຜົນກະທົບ Real-World Usage Scenarios 
 
 
 
 
 APIs Banking: ໃຫ້ແນ່ໃຈວ່າຄວາມຜິດພາດການຢັ້ງຢືນ (ເຊັ່ນ: ຈໍານວນບັນຊີທີ່ບໍ່ມີຕົວແທນ) ບໍ່ເຮັດໃຫ້ບໍລິການ crashed. E-commerce: ການປິ່ນປົວຜົນກະທົບຂອງຜະລິດຕະພັນທີ່ບໍ່ໄດ້ຮັບການຊອກຫາຫຼືການຊໍາລະເງິນຢ່າງງ່າຍດາຍ Data Microservices: Returns ຄໍາຮ້ອງສະຫມັກທີ່ສ້າງຕັ້ງຂຶ້ນໃນເວລາທີ່ການເຂົ້າລະຫັດຂໍ້ມູນບໍ່ໄດ້ຮັບການຢັ້ງຢືນ. API Gateway: ການຕອບສະຫນອງທີ່ເຫມາະສົມໃນໄລຍະຫຼາຍ microservices. Final Thoughts ໂດຍການເຊື່ອມຕໍ່ @ControllerAdvice, @ExceptionHandler, ແລະຮູບແບບ Error Response ງ່າຍດາຍ, ທ່ານໄດ້ຮັບ: 
 
 
 
 ລະຫັດ QR ຄວາມຄິດເຫັນທີ່ API ຄວາມງ່າຍດາຍ debugging ໃນການຜະລິດ ມັນເປັນຫນຶ່ງໃນຮູບແບບການອອກແບບຢ່າງງ່າຍດາຍທີ່ສຸດໃນການພັດທະນາ Spring Boot.

This story contains AI-generated text. The author has used AI either for research, to generate outlines, or write the text itself. 

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

Read My Stories

ສຽງນີ້ຖືກຜະລິດເປັນພາສາຕົ້ນສະບັບຂອງເລື່ອງ!

ການອອກແບບລະບົບ API ມີຄວາມປອດໄພ: ການປິ່ນປົວຢ່າງກວ້າງຂວາງທີ່ມີການຄວບຄຸມ Spring Boot

About Author

ຄຳເຫັນ

ວາງປ້າຍ

ບົດຄວາມນີ້ໄດ້ຖືກນໍາສະເຫນີໃນ

Related Stories

New Year, New Exciting Features: Mint Your Name, Watch Web 2.5 and Meet The Top Startups of The Year

What's the History Behind the HackerNoon Logo?

Meet Bird Eye India, Winner of Startups of The Year 2024 in Fashion

Design Shifts at HackerNoon: Streamlined Top Nav, Quick Search and Settings Dashboard 🚀

New Year, New Exciting Features: Mint Your Name, Watch Web 2.5 and Meet The Top Startups of The Year

What's the History Behind the HackerNoon Logo?

Meet Bird Eye India, Winner of Startups of The Year 2024 in Fashion

Design Shifts at HackerNoon: Streamlined Top Nav, Quick Search and Settings Dashboard 🚀

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps

ການອອກແບບລະບົບ API ມີຄວາມປອດໄພ: ການປິ່ນປົວຢ່າງກວ້າງຂວາງທີ່ມີການຄວບຄຸມ Spring Boot

About Author

ຄຳເຫັນ

ວາງປ້າຍ

ບົດ​ຄວາມ​ນີ້​ໄດ້​ຖືກ​ນໍາ​ສະ​ເຫນີ​ໃນ

Related Stories

Light-Mode

Classic

Newspaper

Minty

Dark-Mode

Neon Noir

Minty

HN StartUps

ບົດຄວາມນີ້ໄດ້ຖືກນໍາສະເຫນີໃນ