How pramithamj/fully-completed-microservices-java-springboot works
Project type and purpose
• This is a Java-based, Spring Cloud microservices ecosystem (Spring Boot 3.2.5, Java 17) demonstrating common distributed-system patterns: centralized config, service discovery, API gateway, async messaging, resilience, and tracing.
• The README confirms eight distinct services—Config Server, Eureka Discovery, API Gateway, and six domain services (Customer, Product, Order, Payment, Notification)—plus Kafka for messaging and Zipkin for tracing.
File structure
• Top-level directories:
• services/… (each microservice is self-contained with its own pom.xml, src/, resources, tests, Dockerfile support)
• docker-compose.yml (to orchestrate services in containers)
• resources/… (business needs, curriculum, distributed patterns—reference docs)
• Each service:
• config-server: holds central application.yml fragments for all services
• discovery: Eureka registry
• gateway: Spring Cloud Gateway (routing, circuit breaker)
• customer, product, order, payment, notification: domain microservices, some using Kafka producers/consumers, some REST clients to others.
• Product service also shows Flyway migrations under src/main/resources/db/migration.
• Configuration files (application.yml) use placeholders to pull from Config Server.
• kafka-related configs appear in order, payment, and notification services.
Additional insights from README
• Spring Cloud Config Server backs all service configs.
• Eureka handles service registration and discovery.
• Gateway enforces cross-cutting concerns (resilience, tracing).
• Kafka for events (order placed, payment processed → notification).
• Zipkin traces distributed calls.