meysamhadeli/booking-monolith
64.5
Weak · 8 November 2026
4.9k
lines of production code
C#
primary language
7
measurements over time
What this system is
This system is a .NET 10 booking monolith that manages flight and booking operations through a domain-driven architecture. It exposes API endpoints for creating and managing bookings, flights, aircraft, and airports, utilizing event sourcing for the booking aggregate and MongoDB for read model synchronization. The infrastructure is orchestrated via .NET Aspire, integrating PostgreSQL, EventStoreDB, and RabbitMQ to support distributed observability and messaging.
Features
Initial API service scaffolding with Aspire integration
The API service is initialized with a new infrastructure layer that integrates with .NET Aspire for local development orchestration. This includes a centralized \SharedInfrastructureExtensions\ class that configures the application with JWT authentication, IdentityServer, MediatR with validation and logging behaviors, MassTransit for in-memory messaging, and multiple data stores (PostgreSQL, MongoDB, EventStoreDB). The service also enables distributed observability (OpenTelemetry, Prometheus) and resilience patterns via Aspire's service defaults, while \Program.cs\ wires these components together to expose minimal endpoints.
src/Api · high confidence
Initial Booking Monolith domain scaffolding
This change introduces the initial structure for the Booking Monolith, establishing the foundational domain models and infrastructure for the Flight and Booking aggregates. It defines the core entities (Booking, Aircraft, Airport, Flight, Seat) with value objects and validation logic, sets up the read/write data access layers using Entity Framework Core (PostgreSQL) and MongoDB, and implements event mapping and projection logic to synchronize domain events to the read models.
src/BookingMonolith · high confidence
Initial implementation of Booking and Flight domain features
This change introduces the foundational domain logic and API endpoints for the Booking and Flight modules. For bookings, it adds the CreateBooking endpoint, the Booking aggregate with event sourcing, and associated value objects (PassengerInfo, Trip). For flights, it implements the full CRUD lifecycle (Create, Read, GetAvailable, Update, Delete) via endpoints and handlers, including a MongoDB-based read model synchronization for flight, aircraft, and airport entities. It also adds the underlying domain models and value objects for Aircraft (Name, Model, ManufacturingYear) and Airports (Name, Address, Code), establishing the core data structures and validation rules for the application.
(repo-wide) · high confidence
Project initialized with .NET 10 target and Aspire integration
The repository has been initialized as a booking monolith application targeting .NET 10.0, enforced via \Directory.Build.props\ and \global.json\. This setup includes a new \.dockerignore\ file to optimize container builds and a \Directory.Build.targets\ file that specifically prevents the \Griffin.TestBase\ submodule from being incorrectly identified as a test project. The solution structure incorporates Aspire for service orchestration and observability, alongside a \src/BuildingBlocks\ git submodule pointing to the Griffin library, which provides shared infrastructure such as EF Core, caching, and validation components.
(repo-wide) · high confidence
Behavioural changes
Added commit message linting and pre-commit formatting hooks
The repository now enforces commit message standards and code formatting automatically. A new commit-msg hook runs commitlint to validate commit messages against configured rules, while a pre-commit hook executes npm scripts for formatting and CI-format checks before changes are staged.
.husky · high confidence
Dependencies
Initialize .NET 10 monolith with Aspire hosting and standard tooling
The project is initialized as a .NET 10 monolith, with core libraries and the API service targeting net10.0 and referencing Microsoft .NET 10 packages (e.g., EF Core 10.0.3, ASP.NET Core 10.0.3). An Aspire AppHost is added to manage infrastructure, referencing Aspire.Hosting packages at version 13.1.1 (including Docker, MongoDB, PostgreSQL, RabbitMQ, Redis, EventStore, and Elasticsearch hosts). The build is configured with commitlint and Husky for conventional commits, and integration tests are set up with xUnit and Microsoft.NET.Test.Sdk.
(dependencies) · high confidence
Housekeeping
Added booking monolith architecture diagram
A new architectural diagram (booking-monolith.drawio) has been added to the assets folder, illustrating the system's structure. The diagram depicts a monolith containing Identity, Flight, Passenger, and Booking domains, supported by Postgres, EventStore, and Mongo databases, and an Outbox Processor.
assets · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 65 → 64 (-0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 57 → 57 (-0.0)
- Architecture 91 → 91 (+0.2)
- Maturity 71 → 73 (+2.8)
- Readiness 67 → 67 (+0.0)
- Security 67 → 65 (-1.5)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)
Resolved (7)
- Coverage not measured — no coverage collector is wired up
- In the Flight domain, 'FlightDate' is used for the arrival date (see Property: BookingMonolith.Flight.Flights.Models.FlightReadModel.FlightDate which maps to arrival logic in some contexts, or potentially the main date) while 'DepartureDate' is explicit. If 'FlightDate' represents the departure date, it is inconsistent with 'DepartureDate'. If 'FlightDate' represents arrival, it should likely be 'ArrivalDate' to match the explicit 'DepartureDate' naming convention for clarity. Given Property: BookingMonolith.Flight.Flights.Models.FlightReadModel.ArriveDate exists, 'FlightDate' likely refers to the primary date (often departure), but the name is less precise than 'DepartureDate'.
- Split BookingMonolith
- The concept of a 'Name' is modeled as a Value Object in three different domains (Aircraft, Airport, Passenger). While the naming is internally consistent within each domain, the shared simple name 'Name' across distinct aggregate roots can be ambiguous when referring to the concept generically. However, since they are strictly scoped by their declaring type and namespace, this is a minor style observation rather than a functional inconsistency. No actionable rename is required as the context is clear.
- XML-doc coverage: Api (src/Api/src/Api.csproj)
- XML-doc coverage: BookingMonolith (src/BookingMonolith/src/BookingMonolith.csproj)
- XML-doc coverage: ServiceDefaults (src/Aspire/src/ServiceDefaults/ServiceDefaults.csproj)
New (3)
- Projects may be oversized for their cohesion (src/BookingMonolith/src/BookingMonolith.csproj)
- Split BookingMonolith (src/BookingMonolith/src/BookingMonolith.csproj)
- top-level statements (cyclomatic 16) (src/Aspire/src/AppHost/Program.cs)
API surface
- Unchanged — 1 HTTP endpoints
Architecture
- Unchanged — 3 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
meysamhadeli/booking-monolith was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 36e2feb77730560b36264bc4a47e9899d0460318 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.