search

GFlisch / Arc4u.Guidance.Doc

Other
5 stars 1 forks source link

Moving to Minimal APIs and API Endpoints #23

Open devbrsa opened 1 year ago

devbrsa commented 1 year ago

For some projects the current template becomes challenging from an implementation point of view, sometimes becoming a silver bullet. The vast majority of projects solve themselves with the current architecture, where others have a high business complexity. To this end, the portfolio of new architectural standards could be used. Following the microservices architecture style, services should be leaner and easier to adopt. MinimalApis and ApiEndpoints can help for this evolution, we could use and extract the need for the MVC pattern and use the REPR Design Pattern (Request-Endpoint-Response).

FastEndpoint is a great framework containing all the built-in components needed to implement Minimal APIs. (Routing, Mapping, Validation, etc.), besides that avoid a lot of boilerplate code, also supporting security, OpenAPI/Swagger, etc,

I strongly believe this component deserves a try, following the idea of request/response and delegating, FluentValidation at model binding and so on.

rdarko commented 1 year ago

This is not planned to be done for the .net 6