Skip to content
Clean Minimal API
Lean Mean Clean Apps

Five templates, one search box. Everything in the docs is in here, including the bits we hoped you'd skim.

Try one of these

Results say which template they came from, so you won't end up reading about Lambda when you wanted GraphQL. Again.

Architecture

This solution is loosely based on Clean Architecture. It’s by no means perfect, so we prefer to call it Lean Mean Clean Architecture. The inspiration is Jason Taylor’s Clean Architecture template, with some ideas taken further and others scaled back.

Dependencies point inwards

Section titled “Dependencies point inwards”

Application sits in the middle and depends on nothing. Presentation and Infrastructure sit around the outside, and both depend on Application. The outside can change without the middle noticing.

PRESENTATIONINFRASTRUCTUREAPPLICATIONdepended on by everyonePresentationHTTP endpoints, OpenAPI and Scalar.ApplicationEntities, rules, queries and validation.InfrastructureSQLite, EF Core and the repositories.
  1. Presentation exposes the Application layer as Minimal API endpoints. Each endpoint reads the route, query string or body, sends a command or query through Mediator and returns the result, and one exception handler turns Application errors into Problem Details.
  2. Application owns the domain and the business logic. Commands and queries are validated and handled here, and each domain type has its own repository interface. Application doesn’t care what fulfils those contracts, as long as something does.
  3. Infrastructure owns the data. It implements the repository interfaces and maps its own data models onto the Application entities, so persistence details don’t leak upwards.

There’s a little CQRS in the style of the commands and queries, but reads and writes use the same database underneath. CQRS-curious, if you like.

The one rule we bend

Section titled “The one rule we bend”

In textbook Clean Architecture, Presentation never references Infrastructure. Here it does, so it can wire up dependency injection without a fourth project whose only job is to call two methods.

To keep that from turning into a free-for-all, every class in Infrastructure is internal. Presentation can call AddInfrastructure and nothing else. If you try to new up a repository from an endpoint, the compiler will politely decline.

What happens on a request

Section titled “What happens on a request”
EndpointMediatorValidationHandlerRepositoryPresentationApplicationInfrastructure
  1. ASP.NET Core matches the route and binds the parameters, then calls the static endpoint handler.
  2. It sends a command or query through Mediator, with the request’s cancellation token.
  3. The ValidationBehaviour runs every FluentValidation validator for the request. Any failure stops here with a ValidationException.
  4. The handler calls a repository interface.
  5. The repository in Infrastructure runs the query against SQLite with Entity Framework Core and maps the results back to Application entities.
  6. The endpoint returns the entities, System.Text.Json serialises them in camelCase, and the response goes out with the right status code.
Part of Lean Mean Clean Apps

Made by the Lean Mean Clean Apps team with Clean Architecture, strong coffee and a healthy disregard for pomp and ceremony. Not affiliated with Microsoft, AWS, Uncle Bob or anyone with a marketing budget.