Minimal APIs, Clean Architecture: Yes, You Can Have Both

About the session

Minimal APIs are often introduced as a quick and simple way to expose HTTP endpoints. Clean Architecture, on the other hand, is usually associated with more structure and more rules. In real projects, you need a bit of both: the minimalistic approach of Minimal APIs and enough structure to keep the code easy to understand and change over time.

In this session, we’ll build a new Minimal API and look at how to structure it in a clean, practical way. You will see that the endpoints are focused on HTTP concerns only, we’ll move application logic into the correct place, and make sure the domain code does not depend on web or framework details. The goal is not to introduce many layers, but to introduce just enough separation to avoid problems later.

By the end of the session, you’ll have a clear and realistic blueprint for using Minimal APIs with clean boundaries, without adding unnecessary complexity to a small service.