# kgrzybek/modular-monolith-with-ddd

Full Modular Monolith application with Domain-Driven Design approach.

Repository: https://github.com/kgrzybek/modular-monolith-with-ddd
Canonical: https://ross.abutalabs.com/products/modular-monolith-with-ddd
Language: C#
License: MIT
License Family: permissive
Topics: ddd, ddd-architecture, cqrs, architecture, rest-api, dotnet, dotnetcore, clean-architecture, clean-code, domain-driven-design, ddd-cqrs, design-patterns, software-architecture, rest, ddd-example, entity-framework-core, design-systems, modularity, monolith, event-sourcing
Last push: 2024-06-04T17:51:26+00:00

## Health v2 (maintenance only)
Score: 32/100 (v2, computed 2026-09-03T02:20:16.233290+00:00)
- activity 0, release rhythm 35, longevity 100
- inputs: {"age_days": 2568, "days_push": 820, "days_rel": null, "gap_med": null, "n_releases_24m": 0}
- flags: no_releases
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 13962, forks 2182 (observed 2026-08-28T04:11:05.176828+00:00)

## What it is
A full sample .NET application demonstrating a modular monolith architecture built with Domain-Driven Design, CQRS, and clean architecture principles. It serves primarily as an educational reference and architecture blueprint rather than a reusable library.

## Use cases
- learn domain-driven design with a real codebase
- example of modular monolith architecture in .NET
- reference implementation of CQRS and event sourcing
- study clean architecture patterns with Entity Framework Core
- template for structuring a large .NET backend
- learn how to organize modules and integration in a monolith

## When to choose
- you want to learn DDD and CQRS from a complete, well-documented example
- you are designing a modular monolith and need an architectural reference
- you want to see testing, CI, and architecture decision records applied together

## When to avoid
- you need a production-ready framework or starter kit to drop into your project
- you are building microservices rather than a monolith
- your stack is not .NET/C#

## Facets
- artifact type: learning-resource
- maturity: maintenance
- function: web-framework, api-framework, orm, middleware, testing, documentation
- domain: web-development, backend, developer-tools, tutorials, apis
- platform: dotnet, cross-platform
- tags: domain-driven-design, cqrs, clean-architecture, modular-monolith, event-sourcing, entity-framework-core, sample-application, architecture-reference, web-server

## Member repositories
- kgrzybek/modular-monolith-with-ddd (main) score 32

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:05.176828+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:12:55.323046+00:00, confidence not recorded.
  - readme: https://github.com/kgrzybek/modular-monolith-with-ddd (fetched 2026-08-28T04:11:05.176828+00:00, sha f8d4169c89c5)
- Data as of 2026-08-30T08:39:29.467469+00:00.