Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is minimal API meant to replace controllers completely? #15

Closed
dee-cf opened this issue Oct 28, 2021 · 1 comment
Closed

Is minimal API meant to replace controllers completely? #15

dee-cf opened this issue Oct 28, 2021 · 1 comment

Comments

@dee-cf
Copy link

dee-cf commented Oct 28, 2021

I believe title is self explanatory...I couldn't find some insight/discussions/info about what are the long term plans (if there are any) about controllers.

Is some long term plan to have minimal API only and deprecate controllers?

If someone could shed a bit of light it would be highly appreciated.

PS.
not that i'm not used to this node.js express style minimal way, just trying to understand plans if there are any so i could act accordingly.

tnx

@DamianEdwards
Copy link
Owner

There's no plan to deprecate controllers, but we do want Minimal APIs to be able to be used in place of controllers for maybe 80-90% of scenarios. Controllers in ASP.NET Core MVC have many, many features that while powerful add a lot of complexity and, in some cases, ceremony that simply isn't required for a lot of apps. That complexity also adds overhead that means there's a limit to how much we can improve the performance of Controllers before hitting diminishing returns (in truth we're already there).

Expect to see a few more features inspired by MVC coming to routing/Minimal APIs in the future to help round it out, e.g. deferred result execution, and endpoint filters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants