How selin-topcu/spring-boot-microservices-angular-product-project works
Main Components
a. API Gateway Layer:
• API Gateway service as the entry point
• Keycloak integration for security (evident from mysql_keycloak_data)
• Routing configuration (Routes.java)
b. Microservices:
• Product Service (MongoDB-based)
• Order Service (MySQL-based)
• Inventory Service (MySQL-based)
c. Databases:
• MongoDB for Product Service
• MySQL instances for Order and Inventory Services
• Keycloak MySQL database
Component Relationships
• Client requests → API Gateway
• API Gateway → Individual Microservices
• Order Service → Inventory Service (via InventoryClient)
• Services → Their respective databases
Architectural Patterns to Highlight
• API Gateway Pattern
• Microservices Pattern
• Database per Service Pattern
• OAuth2/OpenID Connect (via Keycloak)
[Client Applications] → [API Gateway + Security]
• ↓
[Product Service] [Order Service] [Inventory Service]
• ↓ ↓ ↓
• [MongoDB] [MySQL] [MySQL]
Additional Elements
Include:
• Service Discovery mechanism
• Database migration paths (Flyway present in services)
• Inter-service communication (REST)
Technical Details to Note
For each service, show:
• Spring Boot Framework
• Database Type
• Communication Protocols
• Security Integration Points
Specific Implementation Notes
• MVC pattern within each service:
• Controllers
• Services
• Repositories
• Models/DTOs
Infrastructure Elements
• Docker containers (evident from docker-compose files)
• Volume mounts for persistence
• Network segregation