How pallaveejarad/microservices-backend works
Project Type and Purpose
• This is a backend microservices system built on Spring Boot and Spring Cloud.
• Purpose: Simulate a real-world order processing workflow with service discovery (Eureka), an API Gateway, inter-service communication, resilience patterns, and per-service persistence.
File Structure
• Top-level modules:
• api-gateway (Spring Cloud Gateway)
• eureka-server (Service Registry)
• product-service, order-service, payment-service (individual Spring Boot microservices)
• Each module uses Maven, has its own application.yml, src/main/java entrypoint, and test folder.
• Presence of Resilience4j, WebClient calls in service code (per README) and global exception handlers.
• No frontend—pure backend.
README for Additional Insights
• Ports and responsibilities of each service.
• Tech stack: Java 21, Spring Boot 3.3, Spring Cloud Gateway, Eureka, Resilience4j, WebClient, Spring Data JPA, MySQL.
• Future plans include distributed tracing, config server, Docker.
Essential Architectural Elements
• Circuit-breaker/fallback annotations on inter-service calls.
• Build and deployment hint: Maven wrapper (.mvn), potential Docker in future phases.