How selimhorri/ecommerce-microservice-backend-app works
Project Type & Purpose
• This is a cloud-native, Spring Boot & Spring Cloud–based microservices backend for an e-commerce application.
• It implements key microservices patterns: API gateway, service discovery (Eureka), centralized config, circuit breakers (Resilience4j), event-driven messaging (Kafka), and observability (Zipkin, Prometheus, ELK).
File Structure Analysis
• Top-level modules under the parent POM:
• api-gateway (routes external traffic)
• proxy-client (authentication/authorization service)
• service-discovery (Eureka registry)
• cloud-config (centralized config server)
• user-service, product-service, favourite-service, order-service, shipping-service, payment-service (domain microservices)
• Each microservice has its own Dockerfile, compose.yml, application-{dev,stage,prod}.yml, database migrations, and system.properties.
• Root compose.yml brings up all services plus Kafka and Zipkin.
• K8s folder contains Kubernetes manifests for each component.
• CI/CD workflows under .github/workflows for each service and environment.
README Insights
• Describes a 10-service landscape with Kafka as messaging backbone, Docker Compose for local dev, and plans to migrate to Kubernetes.
• Illustrates system boundary: external clients → API Gateway → proxy-client (OAuth2) → microservices → databases.
• Highlights use of Spring Boot Actuator metrics (Prometheus), Zipkin tracing, and ELK for logging.