How dsvasudev19/capstone-project works
Main components
• API Gateway – Serves as the single entry point for all client requests, handling routing, load-balancing, and authentication.
• Service Registry (Netflix Eureka) – Registers all microservices and enables dynamic discovery.
• Authentication Service – A dedicated service to secure and validate incoming API requests using JWT tokens.
• Carpool Service
• Bus Service (including live bus tracking with integration to Ola Maps)
• User Management Service
• Operator Management Service (if distinct)
• Route Service (for route optimization and planning)
• Notification Service (to push alerts and status updates)
• Feedback Service (to handle feedback submission)
• Payment Service (handling transactions and external payment integrations)
• External integrations – Show connections to PostgreSQL (as the database) and to external services like Ola Maps, plus any third-party payment gateways.
• Frontend – Represent the UserInterface (which appears to use Angular, while the README also mentions React as an optional UI); this communicates with the API Gateway.
Relationships and interactions
• Data flow from the client (frontend application) hitting the API Gateway.
• Bi-directional or one-way interactions between microservices and the Service Registry, which supports dynamic discovery.
• Microservice with its respective data source showing interactions with PostgreSQL instances.
• For live bus tracking, show the Bus Service’s integration with Ola Maps.
Architectural patterns and design principles
• Microservices Architecture: Note the separation of concerns by having each business function (authentication, bus scheduling, route planning, etc.) implemented in its own independent service.
• API Gateway pattern: Emphasize the single access point for external requests that also integrates centralized authentication.
• Service discovery using Netflix Eureka.
• Containerization and orchestration potential by including Docker (and optionally Kubernetes if scaled).
Technologies
• Backend: Spring Boot, Spring Cloud, Spring Security, Spring Data JPA, PostgreSQL, Docker.
• Communication: RESTful APIs with JWT-based authentication.
• External Services: Ola Maps integration for real-time bus tracking.
• Frontend: Modern JavaScript frameworks (Angular for the UserInterface in this codebase, with React as an optional mention).
• Infrastructure: Docker & possible Kubernetes orchestration.
• Network infrastructure components (API Gateway, Service Registry)
• Optionally, group components belonging to similar functions (e.g., core transit functions vs. authentication/security).