abhilashroyal29-afk/microservices_abhilash

Purpose and Runtime

This repository contains two independently buildable Java/Spring Boot microservices: Order Service and User Service. Each Maven module has its own wrapper, POM, application bootstrap, resources, and compiled output. There is no gateway, shared library, container configuration, or orchestration definition shown.

Service Entry Points

Spring Boot starts each service through:

• Order-Service/src/main/java/com/microservice/order/OrderServiceApplication.java

• User-Service/src/main/java/com/microservice/user/UserServiceApplication.java

Runtime properties are service-local:

• Order-Service/src/main/resources/application.properties

• User-Service/src/main/resources/application.properties

Maven build boundaries are Order-Service/pom.xml and User-Service/pom.xml.

Order API and Processing

Order-facing HTTP requests enter Order-Service/src/main/java/com/microservice/order/controller/OrderController.java, which delegates business operations to Order-Service/src/main/java/com/microservice/order/service/OrderService.java.

The order domain is represented by Order-Service/src/main/java/com/microservice/order/entity/Order.java; responses are shaped separately through Order-Service/src/main/java/com/microservice/order/dto/OrderResponse.java. This separates internal order state from the controller’s external response contract.

Order-to-User Dependency Boundary

Order Service explicitly models unavailability of User Service via Order-Service/src/main/java/com/microservice/order/exception/UserServiceUnavailableException.java. Application wiring or client-related configuration is centralized in Order-Service/src/main/java/com/microservice/order/config/AppConfig.java.

The intended control flow is: request → order controller → order service → user-service dependency/validation → order response or translated failure. The precise transport/client implementation is not visible in the tree, but the exception establishes a material cross-service dependency.

User API and Domain

User-facing requests enter User-Service/src/main/java/com/microservice/user/controller/UserController.java and flow into User-Service/src/main/java/com/microservice/user/service/UserService.java.

User persistence/domain state is modeled by User-Service/src/main/java/com/microservice/user/entity/User.java, while API transfer data is represented by User-Service/src/main/java/com/microservice/user/dto/UserDto.java. Missing-user behavior is an explicit domain boundary in User-Service/src/main/java/com/microservice/user/exception/UserNotFoundException.java.

Error and API Boundaries

Each service owns global exception translation at its HTTP boundary:

• Order-Service/src/main/java/com/microservice/order/exception/GlobalExceptionHandler.java

• User-Service/src/main/java/com/microservice/user/exception/GlobalExceptionHandler.java

This keeps controllers/services focused on normal and domain failure paths while consistently converting exceptions into client-facing responses.

Infrastructure Implications

The repository is a pair of separately deployed Spring Boot/Maven runtimes. User Service is an external runtime dependency of Order Service. Persistence technology, service-discovery mechanism, HTTP client choice, authentication, message broker, database schema, and deployment platform cannot be established from the provided files; any graph planner should model them as unresolved rather than inferred.