-
Build sessions: https://youtu.be/l32fiBG9YeQ?t=1823 mentions that minimal APIs is the new recommendation for going forward new webapps.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
Controller based APIs will still be there in the future and you can use them. But minimal APIs is the area where future developments in ASP.NET Core will happen.
It's quite similar to MVC pages <-> Razor pages. Both exists, and provide a different way to achieve the goal. What may happen (my personal opinion) is that some area may get more attention than the other. But this doesn't mean that the other one will be removed or that like. |
Beta Was this translation helpful? Give feedback.
Personal opinion follows.
When it's a new featue, then I'd use minimal APIs.
Extending existing features, then I'd add it to the controller.
When it's easy to migrate, then I'd do it for smaller controllers. But w/ a distinct PR, so that the "touch basis" change doesn't get noise with the migration.
I don't know what your controller / actions are doing. When you have applied a pattern like CQRS or at least anything that offloads the work to specific handlers, then the migration should be quite easy, as it's basically just build…