sanjeevveerapandian/booking-system-api

Purpose and runtime

MovieBooking is a layered ASP.NET Core backend for cinema operations: identity, theater/movie/show administration, seat selection, booking, payment, invoicing, and ticket delivery. The HTTP host starts in MovieBooking.API/Program.cs; endpoint groups are implemented as MVC controllers under MovieBooking.API/Controllers.

Composition and dependency boundaries

The solution separates API delivery, application use cases, persistence, and infrastructure adapters. Dependency injection is assembled through MovieBooking.Application/Extensions/ApplicationServiceRegistration.cs, MovieBooking.Persistence/Extensions/PersistenceServiceRegistration.cs, and MovieBooking.Infrastructure/Extensions/InfrastructureServiceRegistration.cs. Application services depend on interfaces; persistence and infrastructure provide implementations.

HTTP API and authorization edge

Controllers expose resource-oriented operations for auth, bookings, catalog, venues, shows, payments, invoices, tickets, and administration. Key entry points include MovieBooking.API/Controllers/AuthController.cs, MovieBooking.API/Controllers/BookingsController.cs, and MovieBooking.API/Controllers/AdminController.cs. JWT issuance is abstracted by MovieBooking.Application/Interfaces/IJwtTokenGenerator.cs and implemented in MovieBooking.Infrastructure/Security/JwtTokenGenerator.cs, making authentication an infrastructure boundary.

Core booking lifecycle

Booking is the central transactional workflow: requests use booking DTOs, the application service coordinates availability and persistence, and booking/seat associations represent reserved seats. Primary paths are MovieBooking.Application/Services/BookingService.cs, MovieBooking.Application/DTOs/Booking/CreateBookingDto.cs, MovieBooking.Persistence/Models/Booking.cs, and MovieBooking.Persistence/Models/BookingSeat.cs. Seat availability is a separate service/repository concern through MovieBooking.Application/Services/SeatService.cs and MovieBooking.Persistence/Repositories/SeatRepository.cs.

Cinema catalog and scheduling

Theater, screen, seat, movie, and show services form the scheduling hierarchy that booking consumes. Relevant components are MovieBooking.Application/Services/TheaterService.cs, MovieBooking.Application/Services/ScreenService.cs, MovieBooking.Application/Services/ShowService.cs, plus persisted models MovieBooking.Persistence/Models/Theater.cs, MovieBooking.Persistence/Models/Screen.cs, and MovieBooking.Persistence/Models/Show.cs. Movie metadata is managed independently by MovieBooking.Application/Services/MovieService.cs and MovieBooking.Persistence/Models/Movie.cs.

Financial and fulfillment stages

After booking, payment, invoice, and ticket services model downstream commercial artifacts. The main application stages are MovieBooking.Application/Services/PaymentService.cs, MovieBooking.Application/Services/InvoiceService.cs, and MovieBooking.Application/Services/TicketService.cs; persisted financial records are MovieBooking.Persistence/Models/Payment.cs and MovieBooking.Persistence/Models/Invoice.cs. Generated ticket PDFs are served from API static content under MovieBooking.API/wwwroot/tickets.

Persistence and external services

Entity Framework-style data access is centralized in MovieBooking.Persistence/Context/MovieBookingDbContext.cs, with entity-specific repository interfaces/implementations such as MovieBooking.Persistence/Repositories/IBookingRepository.cs and MovieBooking.Persistence/Repositories/BookingRepository.cs. SMTP email is an external integration behind MovieBooking.Application/Interfaces/IEmailService.cs, implemented by MovieBooking.Infrastructure/Email/EmailService.cs; email logging is represented by MovieBooking.Persistence/Models/EmailLog.cs.