How akimushkin/airlinebookingsystem works
Project type and purpose
• This is a .NET-based, microservices-oriented full-stack backend for an airline booking system.
• It follows a “Clean Architecture” or “Onion Architecture” approach in each microservice, with clearly separated API, Application, Core, and Infrastructure layers.
• It consists of four business-capability services—Bookings, Flights, Payments, Notifications—each exposed as its own HTTP API.
File structure
• Top-level solution file (.sln) and a folder per microservice:
• AirlineBookingSystem.Bookings.Api + .Application + .Core + .Infrastructure
• AirlineBookingSystem.Flights.Api + .Application + .Core + .Infrastructure
• AirlineBookingSystem.Payments.Api + .Application + .Core + .Infrastructure
• AirlineBookingSystem.Notifications.Api + .Application + .Core + .Infrastructure
• Each “Api” project contains controllers and HTTP request examples (.http), plus appsettings.json for configuration.
• Each “Application” project defines CQRS commands, queries, and handlers.
• “Core” defines domain entities and repository interfaces.
• “Infrastructure” provides repository implementations (e.g., EF Core or Dapper to a Postgres DB).
• An InitialDataSchema folder contains SQL scripts and Docker commands for Postgres and Redis provisioning.
README
• The README is minimal, but the file layout strongly conveys that the solution is built around separate bounded-context microservices, each following the same layered pattern.
• The presence of Postgres and Redis scripts suggests relational storage and a caching or pub/sub layer.
Essential architectural elements
• Four microservices and their layered structure.
• Data stores per service.
• Service composition workflow: flight lookup, payment processing, notification sending.
• Do not include internal file names—focus on logical components and layers.