How ryansilva2004/cricstatlk works
Main Components
• API Gateway – Acts as the single entry point for client requests and aggregates responses from various microservices.
• Microservices – Each is dedicated to a specific domain:
• Player Service: Handles player details.
• Match Service: Manages match information.
• Team Service: Manages team data.
• Performance Service: Records performances.
• Statistics Service: Aggregates and computes statistics.
• Frontend – Implements the user interface using Next.js, consuming the API Gateway’s endpoints.
• (Optional) Shared Infrastructure – Although not explicitly shown in the repository, consider representing common concerns like a database layer for each service or any shared message broker if used.
Relationships and Interactions
• The Frontend sends requests to the API Gateway.
• The API Gateway routes these requests to the appropriate microservice(s) based on the domain (players, matches, teams, etc.).
• Microservices might interact with their own databases (each project contains its configuration under src/main/resources with properties files).
Architectural Patterns and Design Principles
• Microservices Architecture: Each service is decoupled and focused on a single business capability.
• API Gateway Pattern: All external requests are funneled through one entry point.
• Modular Design: Spring Boot is used for individual domain services, ensuring scalability and maintainability.
• Separation of Concerns: Frontend (Next.js) is separated from backend operations (Spring Boot microservices).