MMCA.Common.Testing.E2E 1.128.0

MMCA: Modular Monolith Clean Architecture

A .NET 10 framework for building a modular monolith you can extract services out of later, without a rewrite.

Why it exists

Most teams face the same fork: start as a monolith and pay for it when you need to scale a piece of it, or start with microservices and pay for it immediately. MMCA takes the first path and removes the later cost. Modules are discovered and registered in dependency order, each owns its own database and transactional outbox from day one, and application code talks to abstractions (IMessageBus, INavigationPopulator, repositories) while transport choices stay at the edges. Lifting a module into its own gRPC service changes hosting and configuration, not your handlers.

What comes in the box:

• DDD + CQRS with rich aggregates, static factories returning Result<T>, and a Scrutor decorator pipeline (feature gate, logging, caching, validation, transactions) that wraps every handler without touching one.
• The Result railway instead of exceptions for expected failures, mapped consistently to HTTP Problem Details (RFC 9457) and gRPC status.
• Transactional outbox persisted atomically with your data, drained per data source, at-least-once, with OpenTelemetry metrics.
• Database-per-module over one context class per engine, with cross-source relationships degrading automatically instead of breaking.
• Auth at the edge: JWKS cross-service validation with no shared secret, permission-based authorization, rotating refresh tokens, idempotency keys, and rate limiting.
• Architecture that fails the build: a compile-time layer guard plus a shared NetArchTest rule library, re-run identically in every consuming repo (counts in FACTS.md).

The framework is not a demo. It runs two production applications (a conference platform and an e-commerce store) plus a minimal reference app, and it is graded against a published 34-category rubric with the gaps left visible.

Install

dotnet add package MMCA.Common.API

Each package transitively includes the layers below it (API -> Infrastructure -> Application -> Domain -> Shared), so one reference is usually enough to start. Requires .NET 10 with LangVersion: preview (the DI registration uses C# extension types).

Try it in 15 minutes

MMCA.Helpdesk is the runnable seed: one Tickets module exercised end to end through all five layers, monolith-first, with the extraction path already in place. Clone it, run dotnet run --project Source/Hosting/MMCA.Helpdesk.AppHost, and read Getting Started alongside it: every step in the guide maps to real code in that repo.

Documentation

The full reference library is published at https://ivanball.github.io/docs/:

• Architecture Decision Records: the context, decision, and trade-offs behind every cross-cutting pattern. That index owns the canonical count and range.
• Getting Started: standing up a new application, a module vertical slice, the Aspire host, the fitness map, and a worked service extraction.
• Onboarding guide: a chapter-per-subsystem walkthrough of every first-party type.
• Architecture scorecard: the framework graded against the 34-category rubric, with every score citing the code that earns it.
• Article series: long-form deep dives on the patterns above, each one grounded in this source.

Packages

Every package ships at the same version and is bumped in lockstep (ADR-016). The authoritative list lives in FACTS.md.

Packages are published to nuget.org and mirrored to GitHub Packages (ADR-053).

Built on it

• MMCA.Helpdesk: the minimal reference app and the companion to Getting Started.
• Two production applications (conference platform, e-commerce store) track the framework in lockstep and are the source of the case-study material in the docs.

Contributing

main is protected: branch, open a pull request, let the required checks go green, then squash-merge. See CONTRIBUTING.md for the exact checks and CLAUDE.md for package layout and layer dependency rules.

License

Apache License 2.0, see LICENSE. The license includes an express patent grant from contributors to users.