No video :(

.NET 🔥🚀 : What are Middlewares and how we can leverage our APIs with it?

Подписаться 24 тыс.

Просмотров 3,3 тыс.

50% 1

In this video we will discussed .NET Middleware and how we can use it in our web api
Support me on Patreon to access the source code:
/ mohamadlawand
Base App: • .NET 7 💥 - ASP.NET C...
Let us connect:
🌍 My website - mohamadlawand.com
📸 Instagram - / mohamadlawand087
🐦 Twitter - / moe23
♯ Github - github.com/moh...
🎫 LinkedIn - / mlawand
💥 LinkTree - linktr.ee/moha...
Discord - / discord
Gear I use (affiliate link): amzn.to/3EbT8Jw
Support my work:
/ mohamadlawand
www.buymeacoff...
Hire Me:
transactions.s...
WHO AM I:
I'm Mohamad, a Enterprise Architect working in Manchester, UK. I make videos about web, cloud, desktop and mobile development.
GET IN TOUCH:
If you’d like to talk, I’d love to hear from you. Tweeting @moe23 directly will be the quickest way to get a response, but if your question is very long, feel free to email me at hello@mohamadlawand.com.
#dotnet #api #middleware

Опубликовано:

22 авг 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 19

@saddamhossaindotnet 6 месяцев назад

This is an awesome tutorial. I loved the way you explained everything!

@issamboutissante1542 6 месяцев назад

Thank you for the explanation Mohamad, I love how you are organizing your videos!

@clivebird5729 3 месяца назад

Excellent middleware description!

@abudavid5929 2 месяца назад

Good tutorial

@ala24531 6 месяцев назад

Good job! Why would we add the middleware as a transient and not a scoped service?

@gileee 6 месяцев назад

My favorite way to build services. .NET definitely stole this pattern from Node frameworks like Express/Koa.js and it's awesome. Makes it so easy to see *exactly* the path a request takes through the system, including business logic layers if you also extend this layering approach to them (like by using Optional/Maybe and chaining everything one after the other) It's just so nice to be asked why, where and when something happens to a request and then pulling up a complete journey of that kind of request though the system. It also makes it trivial to implement a sort of railway oriented approach, ie. the two paths approach. The happy path and the unhappy (request rejected for some reason) path. Since you either call the next middleware in the chain, or you return early with an error by simply not calling the next middleware.