Moving from Controllers to .NET Minimal APIs

preview_player
Показать описание
If you are wondering how to move your .NET MVC API Controllers to Minimal APIs, this video is for you.

🚨 KEY LINKS

👋 HEY FRIEND
If you're new to my Channel, my name is Guilherme, but you can call me Gui if Portuguese pronunciation is not your thing.
I see myself as a Minimalist Software Craftsman. That says a lot of what I talk about here.
So, why this YouTube channel? To share with you to simplify your life as a Developer through knowledge, technology, and practices.
If you are into those things as I do, don't forget to subscribe for new videos.

🔗 GET IN TOUCH

#dotnet #cleanarchitecture
Рекомендации по теме
Комментарии
Автор

Great video Gui, I like the approach you have taken. It would be really great to see a more conventions based approach for Minimal API as right now we have to configure so much to get the same results (when compared to controllers).

JasonTaylorDev
Автор

I use Minimal API for small services while using Clean Architecture for bigger projects. I don’t think they replace each other, they are both useful tools.

DarpaProperty
Автор

What is the benefit of going through all that trouble? Don't fix it, if it ain't broken! Using Controllers will always make more sense to me.

everyonesview
Автор

Really useful to see a migration.

How do you know when a traditional API is going to be more suitable than a minimal one?

FroboDaggins
Автор

Great video, great explanation. I just have one question: why should I move away from controllers into minimal apis? Is it more performant? The old ones are deprecated and eventually will be dropped? Why?

rjcarneiro
Автор

How do you unit test your minimal api endpoints?

tobey
Автор

I dont get it you write more code with MINIMAP API how they are minimal when you write more code? i dont like them ....

darkogele