.NET 6 Minimal API vs. Web API 🚀 Complete CRUD with EF Core InMemory

📚 My .NET & Blazor Udemy Courses:
---

📑 Table of Contents:
00:00 .NET 6 Minimal API vs. Web API
02:59 Create a Minimal API Project
05:24 Create a Controller (Web API)
06:54 Add a VideoGame Model
08:54 Add Entity Framework Core InMemory
09:58 Implement the DbContext
11:32 Register the DbContext
12:41 Start implementing the CRUD operations (Web API)
14:17 GET Implementations (Minimal API)
15:24 Test GET Calls with SwaggerUI
16:24 POST Implementations (Web API)
17:35 POST Implementations (Minimal API)
19:02 Test POST Implementations
21:14 GET a Single Game (Web API)
22:37 GET a Single Game (Minimal API)
25:37 PUT Implementations (Web API)
27:54 PUT Implementations (Minimal API)
30:24 DELETE Implementations (Web API)
31:39 DELETE Implementations (Minimal API)
33:40 Quick Recap
35:23 Closing Words

#DotNet #WebAPI #PatrickGod

[alextiger]

thanks man, fantastic stuff. Minimal ApI rocks

[R]

Sweet video, Patrick! I had been curious about this, so thank you for taking this deeper dive!

[ThePredictR]

Thanks for doing this comperation, It helped a lot for me.

[charliehager]

5 stars for the video Patrick! Looks but if minimal API adds everything to middleware why not just get rid of the API all together and go with azure functions and azure sql?

[diligencehumility]

I think we developers have a tendency to be excited for and use brand new technologies (in real world production environment) way too often. It's not what our customers want, and often leads to problems you could easily avoided, by using battletested frameworks.
The minimal API does not support a wide range of features compared to regular API, one of which is versioning.
While I'm also excited for new tech, I would recommend to use battletested technologies for production. Neither your customer or the app users will ever know if it was regular or minimal API underneath, but they will know when the service is not working - and they prefer up-time over anything else

[oncalldev]

Not sure if I would want to use minimal APIs. I don't really see the benefit. I'll stick with Controllers for now, but I am intrigued by APIEndpoints - need to do some additional research there. As always, thanks for the video.

[robledes]

I suppose that if the response time is faster with a minimal API, it will be better to use it for servers with many requests. On the other hand, if the APIs are very large it can be confusing to keep all the code in the Program.cs file, in which case it would be better to have it organized in a controller. Is there any way to externalize the code from Program.cs pointing to another file that contains only the code with the API's? That might be the best solution.

[pavelsvarc]

Very nice, my question is, where are data after close/ shuthdown api project? it is saved to some temporary file or completely cleaned. Thanks

[sylinxstark]

Hello Patrick. Do you have any course that is include .Net application works with WPF application that is for set configuration settings and run application based on user credentials. I would like to watch or buy that course. Thank you. Your videos are very educational.

[olimss]

Hello Bro I'm learning a lot of things from your videos and I think after getting the job I may purchase coffee from my first salary .

[chrisbaker]

If you are putting together a prototype (or even a very small app, perhaps it's a microservice) I could see the benefit of using minimal API. However, for anything reasonably large (more then 2 endpoints) it makes understanding/maintaining the code a potential nightmare.

[DineshKumar-vusg]

You look like Dale Steyn of cricket world 🏏. When I first saw your photo WTF Steyn in .Net. Anyhow nice tutorial. Thanks for this.

[tchinnarao]

please stop back ground music, really bothered me, please please consider in you future videos, more over i bought your course in udemy also, i like that course, super serious this music disraction