REPR (Request-Endpoint-Response) Pattern Will Make Your APIs Clean

☄️ Master the Modular Monolith Architecture: https://bit.ly/3SXlzSt
📌 Accelerate your Clean Architecture skills: https://bit.ly/3PupkOJ
🚀 Support me on Patreon to access the source code:   / milanjovanovic  

Layered architectures, such as Clean architecture, organize the solution across layers. This results in a folder structure grouped by technical concerns. Vertical slice architecture, on the other hand, organizes the code around features or use cases. An exciting approach to structuring APIs around features is using the REPR pattern. It stands for Request-EndPoint-Response. This aligns perfectly with the idea of vertical slices. You can achieve this with the MediatR library, for example. I will show you how to implement the REPR pattern with Controllers, Api.Endpoints, and FastEndpoints.

Check out my courses: https://bit.ly/3PupkOJ

CQRS Pattern With MediatR
https://www.milanjovanovic.tech/blog/...

Vertical Slice Architecture
https://www.milanjovanovic.tech/blog/...

Join my weekly .NET newsletter:
https://www.milanjovanovic.tech

Read my Blog here:
https://www.milanjovanovic.tech/blog

Chapters
0:00 What is the REPR pattern?
1:36 REPR pattern using Controllers
2:45 REPR pattern using Ardalis.ApiEndpoints
8:24 Remark: Fluent generics in C#
9:54 REPR pattern using FastEndpoints