Sign in to track progress and bookmarks.
The Presentation Layer is the face of your application. It could be a Web API, a Blazor WASM app, or even a Command Line tool.
If you are using Clean Architecture correctly, your Controllers should be **Incredibly Thin**. They should do three things:
1. Accept the HTTP request.
2. Send the command/query to MediatR (the Application Layer).
3. Return the result with the correct HTTP status code.
The Presentation layer is responsible for things like **Swagger/OpenAPI** documentation, **CORS** policies, and **Authentication** schemes. It translates the technology-specific details of HTTP into the technology-neutral language of your application's use cases.
Q: "Can I have multiple presentation projects?"
Architect Answer: "YES! This is one of the biggest benefits of Clean Architecture. You could have a **Web API** project for your mobile app, and a separate **Worker Service** project for background processing, and both of them reference the SAME **Application** and **Domain** layers. Your business logic is reused perfectly across multiple entry points."
Quizzes linked to this course—pass to earn certificates.
On this page
1. Thin Controllers 2. Handling Input and Output 3. Architect Insight