How program-guru/aviation-ticketing-system works
Project Type and Purpose
• This is a microservices-based Aviation Ticketing System.
• It handles user management, authentication, flight/airport data, schedules, bookings, and payments.
• It uses domain-driven design, with each bounded context implemented as an independent Spring Boot service.
File Structure
• Top-level directories:
• api-gateway – entry point (Spring Cloud Gateway)
• auth-service – JWT authentication/authorization
• user-service – user CRUD, MySQL persistence
• airport-service – airport CRUD, MySQL persistence, RabbitMQ publisher
• flight-service – flight CRUD, MongoDB, RabbitMQ publisher
• schedule-service – schedule CRUD, MongoDB, RabbitMQ consumer, WebSocket notifications
• booking-service – booking logic, synchronous Feign calls to user, schedule, payment; MongoDB persistence
• payment-service – Razorpay integration, synchronous Feign from booking
• eureka-server – service registry
• docker-compose.yml & k8s/ – container and Kubernetes manifests for all pieces
• Configuration files reveal use of Feign Clients for RPC, RabbitMQ for events, JWT and Spring Security, Docker, Kubernetes.
Key Architecture Insights from README
• API Gateway routes all client calls, enforces JWT security.
• Eureka Server for service discovery/load balancing.
• Synchronous flows use Feign: API→Auth→User, Booking→Schedule, Booking→Payment, Schedule→Flight, etc.
• Asynchronous flows use RabbitMQ: Airport publishes status changes → Flight consumes; Flight publishes updates → Schedule consumes.
• Persistence: MySQL for User & Airport, MongoDB for Flight, Schedule & Booking, external Razorpay for payments.
• Additional real-time updates via WebSocket in Schedule and User services.