How byakif/akif-airlines works
Project Type and Purpose
• This is a full‐stack ASP.NET Core MVC web application (“Akif Airlines”) for online airline ticket management.
• Key indicators:
• A single .NET solution with MVC folders (Controllers, Views, Models).
• EF Core migrations in “Migrations” folder.
• Static assets under “wwwroot” (CSS, JS, Bootstrap, images).
High-Level Architectural Overview
• Layered MVC structure:
• Presentation Layer: Razor Views (.cshtml) + Static Assets (wwwroot)
• Controller Layer: HTTP routing → Controllers
• Business Logic / Services Layer: custom services (LanguageServices)
• Data Access Layer: Entity Framework Core (BiletContext in Models)
• Database: relational DB (e.g., SQL Server) managed via EF Core migrations
Main Components
• Web Browser / Client – issues HTTP(S) requests, renders HTML/CSS/JS.
• ASP.NET Core Web Server – hosts the application (Program.cs, Startup config).
• MVC Controllers – e.g., HomeController, BiletController, AdminController, KullaniciController, etc.
• Razor Views – UI templates under Views/<ControllerName> and Shared layouts.
• Services – LanguageServices for localization.
• EF Core DbContext – BiletContext interacts with database, tracked via Migrations.
• Relational Database – stores entities: Users (Kullanici), Tickets (Bilet), Flights (Ucus), Planes (Ucak), Cities (Sehir), Seats (Koltuk), Roles (Roller).
• Static File Server – serves CSS, JS, images, Bootstrap, jQuery libraries.
• Resource Files – .resx for localization (SharedResource.en-US, tr-TR).
Relationships and Data Flows
• Browser → HTTP GET/POST → ASP.NET Core routing → Controller action
• Controller → injects Services and DbContext → executes business logic / data queries
• DbContext → SQL queries → Database → entity objects
• Controller → passes Model to Razor View → renders HTML → sends back to Browser
• Browser → fetches static assets (CSS/JS) from wwwroot
Architectural Patterns & Principles
• MVC (Model-View-Controller) separation of concerns.
• Dependency Injection for Services and DbContext.
• Repository‐like pattern via EF Core DbContext.
• Localization via resource files and a LanguageServices abstraction.
• Code‐first migrations to evolve database schema.
Technologies & Frameworks
• ASP.NET Core MVC, .NET runtime (Program.cs, launchSettings.json).
• Entity Framework Core for ORM and Migrations.
• Razor for server‐side HTML templating.
• Bootstrap + jQuery for front-end styling and validation.
• JSON configuration (appsettings.json) for environment settings.
Deliverables
• An external static file server (if using CDN or local wwwroot).