Scribd
Upload
15 views4 pages

New Microsoft Word Document (3)

The document outlines a global exception handling strategy for a microservices-based e-commerce platform using Spring Boot. It details the creation of a standardized API response structure and the implementation of a global exception handler with specific methods for different exception types. The approach ensures consistent JSON responses during failures, enhancing the reliability of the API.

Uploaded by

rahulbadhe630
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
15 views4 pages

New Microsoft Word Document (3)

The document outlines a global exception handling strategy for a microservices-based e-commerce platform using Spring Boot. It details the creation of a standardized API response structure and the implementation of a global exception handler with specific methods for different exception types. The approach ensures consistent JSON responses during failures, enhancing the reliability of the API.

Uploaded by

rahulbadhe630
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Context: These questions and answers are for a senior

Java developer with 3 years of experience working on a


complex microservices-based e-commerce platform. The
platform uses Spring Boot, Spring Cloud, Docker, and
various AWS services. The developer has implemented
custom exception handling, security with JWT and
WSO2, distributed logging with ELK stack, and various
design patterns including CQRS and SAGA. The
interview is for a Senior Java Developer position at a
large enterprise that values both theoretical knowledge
and practical implementation skills.
Exemplar Element
text
Exemplar Question and Answer:

Q: "In your e-commerce platform, you noticed that when


the brands microservice fails, it returns HTML error
pages instead of consistent JSON responses. How would
you implement a global exception handling strategy to
ensure all API responses maintain a consistent format
even during failures?"

A: "To solve this inconsistency, I would implement a


global exception handling strategy using Spring Boot's
@ControllerAdvice and @ExceptionHandler annotations.
Here's my approach:

1. First, I'd create a standardized response structure:


public class ApiResponse<T> {
private boolean success;
private T data;
private ErrorDetails error;
// Constructors, getters, setters
}
public class ErrorDetails {
private String code;
private String message;
private String timestamp;
private List<String> details;
// Constructors, getters, setters
}
text

2. Next, I'd implement a global exception handler:


@ControllerAdvice
public class GlobalExceptionHandler {
text
@ExceptionHandler(ResourceNotFoundException.class)
public ResponseEntity<ApiResponse<Void>>
handleResourceNotFoundException(ResourceNotFoundE
xception ex) {
ErrorDetails error = new
ErrorDetails("RESOURCE_NOT_FOUND", ex.getMessage(),
LocalDateTime.now().toString(),
Collections.singletonList(ex.getResourceId()));
return new ResponseEntity<>(new
ApiResponse<>(false, null, error),
HttpStatus.NOT_FOUND);
}

@ExceptionHandler(ValidationException.class)
public ResponseEntity<ApiResponse<Void>>
handleValidationException(ValidationException ex) {
ErrorDetails error = new
ErrorDetails("VALIDATION_FAILED", "Validation failed",
LocalDateTime.now().toString(),
ex.getValidationErrors());
return new ResponseEntity<>(new
ApiResponse<>(false, null, error),
HttpStatus.BAD_REQUEST);
}

@ExceptionHandler(Exception.class)
public ResponseEntity<ApiResponse<Void>>
handleGenericException(Exception ex) {
ErrorDetails error = new
ErrorDetails("INTERNAL_SERVER_ERROR", "An
unexpected error occurred",
LocalDateTime.now().toString(),
Collections.singletonList(ex.getMessage()));
return new ResponseEntity<>(new
ApiResponse<>(false, null, error),
HttpStatus.INTERNAL_SERVER_ERROR);
}
}
text

3. For complete coverage, I'd also customize the error


attributes in Spring Boot:
@Component
public class CustomErrorAttributes extends
DefaultErrorAttributes {
@Override
public Map<String, Object>
getErrorAttributes(WebRequest webRequest,
ErrorAttributeOptions options) {
Map<String, Object> errorAttributes =
super.getErrorAttributes(webRequest, options);
ApiResponse<Void> response = new
ApiResponse<>(false, null,
new
ErrorDetails(errorAttributes.get("status").toString(),
errorAttributes.get("message").toString(),
errorAttributes.get("timestamp").toString(),
Collections.singletonList(

You might also like