mehdihadeli/food-delivery-modular-monolith
44.9
Weak · 8 November 2026
9k
lines of production code
C#
primary language
7
measurements over time
What this system is
This system is a modular monolith food delivery backend built on .NET 10, structured into isolated Catalog, Identity, Customers, and Orders modules. It provides core domain capabilities for managing product catalogs, handling user authentication and registration, and maintaining customer profiles. The architecture leverages PostgreSQL and MongoDB for persistence, with Wolverine facilitating durable in-process messaging and event handling across the modules.
How it got here
2022 — Initial project scaffolding and .NET 10 upgrade
6 changes.
The project was initialized with a modular monolith architecture targeting .NET 10, establishing core infrastructure including PostgreSQL and MongoDB persistence, Wolverine messaging, and centralized build configurations. Initial domain modules for Catalog, Identity, and Customers were scaffolded alongside comprehensive integration test fixtures using Testcontainers.
2024–2026 — Initial modular monolith scaffolding
7 changes.
This period established the foundational architecture of the application as a modular monolith, wiring together core infrastructure components such as Wolverine messaging, PostgreSQL, and JWT authentication. It introduced the initial API endpoints for the Catalog, Identity, and Customers modules, alongside comprehensive test suites and development tooling including Aspire orchestration and Husky hooks.
Features
Added Aspire orchestration and pre-commit code quality hooks
Developers now benefit from automated local environment setup and code quality enforcement. The project introduces an Aspire AppHost configuration that orchestrates the API service with Postgres and MongoDB, handling connection strings and dependencies automatically. Additionally, a new pre-commit hook workflow is established via Husky to automatically format C\# code with CSharpier, verify project style, run analyzers, and restore tools before changes are committed, ensuring consistent code standards.
.husky, src/Aspire · high confidence
Added REST client request files for catalog, customer, and identity APIs
New \.rest\ files have been added to the \\_httpclients\ directory to support the VS Code REST Client extension. These files provide pre-configured HTTP request templates for interacting with the local API at \localhost:5000\, covering authentication, user registration, product catalog management, and customer restock subscriptions.
_\httpclients · high confidence
Added logout endpoint and .NET 8 dev container configuration
The application now includes a new logout endpoint at the identity module's prefix (/logout) that signs out the user and returns a 200 OK response, requiring authorization and supporting API version 1.0. Additionally, the development environment has been updated to use .NET 8 (specifically SDK 8.0.303) via a new dev container setup, which includes configuration for VS Code, Docker Compose, and necessary fonts.
.devcontainer, src/Modules/Identity/FoodDelivery.Modules.Identity/Identity/Features/Logout · high confidence
Initial API infrastructure and modular monolith wiring
The API project is initialized with a modular monolith architecture, introducing a custom controller activation system that routes requests to isolated module-specific dependency scopes. It integrates Wolverine for durable messaging and event handling, wiring up an in-memory event bus and PostgreSQL-backed message persistence. The setup includes health checks for all four modules (Catalogs, Customers, Identity, Orders), JWT authentication with Admin/User roles, and Swagger/OpenAPI documentation. A Dockerfile is provided targeting .NET 10 Alpine, ensuring proper runtime files and globalization support are included in the container image.
src/Api · high confidence
Initial Catalog module with product, brand, and category management
The Catalog module is introduced, providing the foundational domain models and persistence layer for Brands, Categories, and Products. This includes the database schema (PostgreSQL via EF Core migrations), entity configurations, and data seeding for initial catalog content. The module also defines the Product read model and integrates with a MongoDB read context (CatalogReadDbContext) to support read-side queries, alongside API versioning and endpoint mapping infrastructure.
src/Modules/Catalogs, src/Modules/Customers, src/Modules/Identity · high confidence
Initial product catalog API endpoints and domain logic
This change introduces the core product management capabilities for the Catalog module, including creating new products, retrieving them by ID or via a paginated list, and debiting stock levels. It also adds features to update product attributes such as brand, category, supplier, and stock thresholds. The implementation follows a command/query pattern with domain events for side effects like updating product views and handling stock threshold notifications.
(repo-wide) · high confidence
Initial project scaffolding and .NET 10 upgrade
The repository has been initialized with a complete .NET 10 solution structure, including a new solution file, global.json targeting SDK 10.0.100, and mise.toml for tooling. This change introduces a modular monolith architecture with four isolated modules (Catalogs, Identity, Customers, Orders), each with its own dependency injection provider and mediator. It also establishes a PostgreSQL-backed in-process messaging system using Wolverine 6.2 for durable local queues, replacing any previous in-memory or non-durable transport. The project includes comprehensive configuration files (.editorconfig, .csharpierrc, stylecop.json) and a new README documenting the architecture, technologies, and deployment steps.
(repo-wide) · high confidence
New scripts for automated version calculation and release preparation
Added \scripts/calculate-version.sh\ to automatically determine the application version, environment, and Docker tag based on Git refs (tags or main branch) and NBGV output, and \scripts/release-version.sh\ to prepare release trains, release candidates, and stable releases by updating \version.json\ via NBGV.
scripts · high confidence
Behavioural changes
Upgrade to .NET 10 and centralize build configuration
The project targets .NET 10.0, as defined in the new src/Directory.Build.props file, which also centralizes build settings such as implicit usings, nullable context, and code analysis rules. This change introduces a new src/BuildingBlocks submodule and establishes a centralized package management structure via src/Packages.props and src/Directory.Build.targets. While the build system is now configured for .NET 10, the package versions defined in Packages.props (e.g., AspNetCore, Microsoft.Extensions) remain at version 7.0.0.
src · high confidence
Test coverage
Added test suites for Customers and Identity modules; Added tests for user registration in Identity and Customers modules; New shared test infrastructure for integration and end-to-end testing.
Dependencies
Upgrade to .NET 10 and centralize package management
The project has been upgraded to .NET 10, with core libraries such as Entity Framework Core, ASP.NET Core, and Microsoft.Extensions updated to version 10.0.2. Package versions are now centrally managed via Directory.Packages.props, and the solution integrates Aspire (version 9.4) for hosting and service defaults. Additional dependencies include WolverineFx 6.2.0, Swashbuckle 9.0.1, and Duende IdentityServer 7.0.5.
(dependencies) · 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 48 → 45 (-3.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 57 → 57 (+0.0)
- Architecture 58 → 44 (-14.5)
- Maturity 76 → 80 (+4.2)
- Readiness 55 → 57 (+2.3)
- Security 34 → 34 (+0.0)
- Domain Modelling 86 → 82 (-4.6)
- Event-Driven 100 → 100 (+0.0)
- Performance 70 → 64 (-5.3)
Resolved (10)
- Cross-context type ProductCreated (Catalogs → Api) (src/Api/FoodDelivery.Api/Messaging/IntegrationContractHandler.cs)
- Cross-context type ProductStockReplenished (Catalogs → Api) (src/Api/FoodDelivery.Api/Messaging/IntegrationContractHandler.cs)
- Projects may be oversized for their cohesion
- Typo in feature folder name: 'GettingUerByEmail' is a misspelling of 'GettingUserByEmail'. The correct concept is retrieving a user by email, as evidenced by the correctly spelled 'GettingUserById' and the context of the handler.
- XML-doc coverage: FoodDelivery.Api (src/Api/FoodDelivery.Api/FoodDelivery.Api.csproj)
- XML-doc coverage: FoodDelivery.Modules.Catalogs (src/Modules/Catalogs/FoodDelivery.Modules.Catalogs/FoodDelivery.Modules.Catalogs.csproj)
- XML-doc coverage: FoodDelivery.Modules.Customers (src/Modules/Customers/FoodDelivery.Modules.Customers/FoodDelivery.Modules.Customers.csproj)
- XML-doc coverage: FoodDelivery.Modules.Identity (src/Modules/Identity/FoodDelivery.Modules.Identity/FoodDelivery.Modules.Identity.csproj)
- XML-doc coverage: FoodDelivery.Modules.Orders (src/Modules/Orders/FoodDelivery.Modules.Orders/FoodDelivery.Modules.Orders.csproj)
- XML-doc coverage: FoodDelivery.ServiceDefaults (src/Aspire/FoodDelivery.ServiceDefaults/FoodDelivery.ServiceDefaults.csproj)
New (2)
- Projects may be oversized for their cohesion (src/Modules/Catalogs/FoodDelivery.Modules.Catalogs/FoodDelivery.Modules.Catalogs.csproj)
- doc comments repeat the names (src/Modules/Catalogs/FoodDelivery.Modules.Catalogs/Products/Models/Product.cs)
API surface
- Unchanged — 5 HTTP endpoints
Architecture
- Unchanged — 4 containers · 3 contexts · 1 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
mehdihadeli/food-delivery-modular-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 cb7c30c803a293d2257e063f978c80afa62fd8f1 — 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.