How dofire/ez-spring-microservices works
Main components
• API Gateway – s-api-gateway serves as the entry point/client-facing interface that routes incoming requests to the appropriate microservice.
• Domain-specific Microservices – s-user, s-product, s-order, s-payment, and s-notification, each representing distinct bounded contexts.
• Database – A shared PostgreSQL database (or possibly separate logical schemas) that all services connect to using JDBC. The environment variables in the .env sample indicate that they all refer to the same “db” but are configured individually.
• Infrastructure & Deployment – Dockerfile setups for each service, the Docker-compose file (compose.yml) for orchestrating containers, and infras folder for additional configuration (e.g., database initialization).
Important architectural patterns
• Microservices Architecture – Each service is independently developed, deployed, and scaled.
• API Gateway Pattern – Centralizes entry points and possibly handles cross-cutting concerns such as authentication or logging before dispatching to the individual services.
• Containerization – The use of Docker (as indicated by Dockerfiles and compose file) implies that each service and the database run in separate containers.
• Infrastructure-as-Code – The presence of Docker Compose and SQL initialization scripts emphasizes a focus on automation of deployment and environment setup.
Relevant technologies/frameworks
• Spring Boot (Java with the typical src/main/java structure for each service)
• Gradle for build automation
• Docker for containerization and Docker Compose for multi-container orchestration
• PostgreSQL as the backend database
• Clear labels for each component: API Gateway, Notification Service, Order Service, Payment Service, Product Service, User Service, and Database.