Видео

This is the best and simplest explanation I've ever had

Minimal api’s are a gimmick. Just. Say. No.

You forgot to remove the summaries in the traditional controller! thats why the minimal api has less lines of code! 🙂

Are there good opportunities for entry level .net angular dev in australia?

Great content. Do you plan to make a video about Clean Code introduced by Bob with Use cases etc. I am curious about creating Domain scope and for example how to resolve problem that your domain code is not async but application is async and how to handle that case. I am pointing to TypeScript and case where domain return just for example string and use cases need to communicate with BE (repository which return async code). Thanks!

Minimal Api is annoying with repetition of injections but Controllers are a little less performant. Maybe a group injection will help minimal api.

wait 1:46 is that how you do switch-case in C# now? I miss C#

Amazing stuff, to the point and very useful indeed!

your videos are definitely more useful than long&empty chapsas videos. thanks

Great work! awesome examples! Would you mind if I borrow your presentation style and examples for my blog post? I’m covering this topic as well, and I’ll include a link to this video as a reference. Thank you!

Thanks for the video bro, extremetely easy to understand even for a somewhat begginner like me

Means that we have to create a new class for a new NotificationType right?

Great example!

Please can you tell me which software you used to create the video?

It's dependency inversion?

Another great bonus is that the code is more unit test friendly and it's easier to mock things up.

This is more like FastEndpoints does, except it uses minimal API directly, less to minimum dependency which is good. I like the way you explain. It should be understandable even for starter.

I think this is definitely a good approach, however if I'm not mistaken it only allows for one type of notification or am I mistaken?

This is how I see it: When you are in a "selection" scenario: Use strategy. When you are in a "choice" scenario: Use Factory

What I love about minimal api's is that you no longer need to make a large file with all logic, you can put each endpoint in it's own file. great if you want to separate on feature level! Or if you want vertical slice architecture. The lads saying that minimal api's aren't for large projects simply haven't tried our minimal api's. It's perfectly able to do what a controller does, it's just a different flavour.

How do you guys version this appsettings.json files? Do you add it to .gitignore?

Simply awesome 🙌……

bruh, i give up lol, idk why I find this shit so complicated

I love using the strategy pattern with higher order functions: no need to create an interface and classes that implement it. Just create function or directly inject anonymous ones👌

Great video: to the point and full of real life stuff while keeping it simple. Awesome. Subscribed!

Amazing explanation!

Thanks for this! I'm just starting a new Minimal API project and I'm going to use this approach as a template. Don't suppose you fancy revisiting this project to demo how to implement versioning (preferably using the Asp.Versioning.Http package to add URL versioning) with Swagger support too do you!? 😁

Buddy u have added value to my life in just 10 mins. No all other RUclipsrs are able to do that.

really appreciate your efforts ✅

People don't know how to organize minimal apis and yet add 151098310315 handlers for mediatr when adding mediatr for EVERY SINGLE PROJECT. Jesus.

Fantastic tut, cannot get any better from here. Thank you for your amazing work!

Excellent explanation, great job !

Itt the best way to structure code is based on physical locations of the machines involved in running your app. Maybe your app will only ever need to be 1 app, but maybe it will need to be two apps, one which lives in the DMZ and one that lives behind it. So I always go with at least 2 projects. One project is the app and is barebones, and the other project has almost all of the code. This works well in case you need to have two apps or 3 apps, they can all easily share the same codebase.

Very nice montage but please talk little slower ;)

Such a well made video, liked + subbed (if i wasn't already subbed)

Thank you dude 👍🏼

This is surprisingly common thing to do. I didn't know it was called Strategy. Isn't this what interfaces are about?

Really great!! Loved this video

That's too much value in a single video Keep going bud 🎯

This is such a great video, cleared all my confusion on how to match these two patterns in 4 minutes !

Great video. Keep it up.

At 2: When i create an extension method on the PostEntity and then call Select(post => post.toDto()) does this also only take the proeprties i need or does this take all properties and discards the rest again?

For the cartesian explosion issue I think the best approach is to use json functions to return the exact json that you want (e.g., in Postgres you have json_agg function). This way you only have one query to the database and not only you don't return duplicate data, you also return it in a much better format. If you're using Node.js you can immediately use the returned JSON instead of having to map it into objects in your application layer. Not sure if this is supported by .NET and Entity Framework, though.

Confidently incorrect redditor. Nice explanation. +sub

First of all nice video! One point we are missing here is not all endpoints use same dependencies. If only some endpoints are using heavy objects then rest of the endpoints performance degrade if we are using controllers. We can avoid that using minimal api.

Just watched your simple breakdown of the Strategy Pattern and this one. You do have a skill for this. Keep posting, loving this. Subscribed.

Very good content! Congratulations. How can I validate a MapGet with query parameters ? The idea is validate allowed (valid) combinations of five parameters included in the query

This is a very simplistic example that gets messy very quickly. The first problem is putting business logic in your Web Api. You've combined the concerns of the web api, use case and domain logic all into the endpoint. The more complex the logic, the bigger your endpoint becomes. The second problem is that data is now a free-for all that allows unrelated data to intermingle. The bigger the application, the bigger the mess. The vertical slicing is good but needs to be carried through with your data. Move the handler out of your endpoint and call a use case that takes over the work of complex business logic.

The extra indirection can be made easier on the reader by hiding details (i.e. is it multi channel, x channel, y channel???). For example, if the multi channel notifier would have been named just Notifier (in a generic sense), we wouldn't have to care about it being multichannel or whatever, or whatever that means, it would just be a notifier, that uses purpose-build notifiers, like email notifier and sms notifier, but we don't care about that, because our notifier can handle all types of notifications so we can use it everywhere, even where previously an sms notifier was used, or an email notifier was used. By hiding implementation details, including the details of what design patterns are used in the code, we can make it easier for other to read the code and understand what's going on without doing too much digging (i.e. jumping through all the layers of indirection).

Great video, Came across this reddit thread and some of the misinformation in the replies got my piss boiling more than it should have tbh - I do primarily blame Microsoft though for coming up with yet another vague name for a product.