How idzer0/eventmanagementservice works
EventMS is a multi-service event management and booking system. Users authenticate for JWTs, browse or manage events, and submit bookings; booking processing is asynchronous through Kafka, where event-side handling can reserve or release seats. The graph preserves the separate auth, event, booking, and messaging subsystems, including their principal persistence and cache layers. Source excerpts show the API-to-service paths and selected service dependencies; some background-consumer behavior is only identified by registration and file names, so those runtime links are left unasserted or marked unverified.
Main entry points: EventService.cs Event service · AuthService.cs Auth service · BookingService.cs Booking service · AuthController.cs Auth API
Components 20
Authentication
- Auth API
EventMS/Auth/Presentation/Controllers/AuthController.cs - Auth service
EventMS/Auth/Infrastructure/Services/AuthService.cs - JWT generator
EventMS/Auth/Infrastructure/Services/JwtTokenGenerator.cs - User repository
EventMS/Auth/Infrastructure/Repositories/UserRepository.cs - Auth database
EventMS/Auth/Infrastructure/DataAccess/AppDbContext.cs
Event management
- Event API
EventMS/Events/Presentation/Controllers/EventController.cs - Event service
EventMS/Events/Application/Services/EventService.cs - Event repository
EventMS/Events/Infrastructure/Repositories/EventRepository.cs - Event database
EventMS/Events/Infrastructure/DataAccess/AppDbContext.cs - Event cache
EventMS/Events/Infrastructure/Services/RedisCacheService.cs - Request consumer
EventMS/Events/Application/ServicesBackground/BookingRequestConsumer.cs
Booking workflow
- Booking API
EventMS/Bookings/Presentation/Controllers/BookingController.cs - Booking service
EventMS/Bookings/Application/Services/BookingService.cs - Booking repository
EventMS/Bookings/Infrastructure/Repositories/BookingRepository.cs - Booking database
EventMS/Bookings/Infrastructure/DataAccess/AppDbContext.cs - Result consumer
EventMS/Bookings/Application/ServicesBackground/BookingResultConsumer.cs
Messaging
- Kafka publisher
EventMS/Shared/KafkaSettings/Services/KafkaEventPublisher.cs - Kafka consumer
EventMS/Shared/KafkaSettings/Services/KafkaConsumerService.cs - Kafka broker
Other components
- User
Connections 20
- User → Auth API: authenticates
EventMS/Auth/Presentation/Controllers/AuthController.cs - Auth API → Auth service: calls
EventMS/Auth/Presentation/Controllers/AuthController.cs - Auth service → User repository: reads/writes users
EventMS/Auth/Infrastructure/Services/AuthService.cs - Auth service → JWT generator: generates token
EventMS/Auth/Infrastructure/Services/AuthService.cs - User repository → Auth database: persists users
- User → Event API: browses/manages
EventMS/Events/Presentation/Controllers/EventController.cs - Event API → Event service: calls
EventMS/Events/Presentation/Controllers/EventController.cs - Event service → Event repository: queries/updates
EventMS/Events/Application/Services/EventService.cs - Event service → Event cache: reads/writes cache
EventMS/Events/Application/Services/EventService.cs - Event repository → Event database: persists events
- User → Booking API: books/manages
EventMS/Bookings/Presentation/Controllers/BookingController.cs - Booking API → Booking service: calls
EventMS/Bookings/Presentation/Controllers/BookingController.cs - Booking service → Booking repository: reads/writes bookings
EventMS/Bookings/Application/Services/BookingService.cs - Booking service → Kafka publisher: publishes request
EventMS/Bookings/Application/Services/BookingService.cs - Booking repository → Booking database: persists bookings
- Kafka publisher → Kafka broker: publishes messages
- Kafka broker → Result consumer: delivers results
- Kafka broker → Request consumer: delivers requests
- Request consumer → Event service: invokes seat handling
- Kafka consumer → Kafka broker: consumes messages