Task.Run vs Async: The Ultimate Guide to Scalable .NET APIs
Автор: Frontend to Backend with Rohan
Загружено: 2026-01-08
Просмотров: 144
Is Task.Run the same as async/await? Short answer: No. Long answer: Using them incorrectly in ASP.NET Core can actually destroy your application's scalability.
In this video, we break down the fundamental differences between CPU-bound and I/O-bound work. We’ll explore why wrapping synchronous code in Task.Run inside a controller is often a "fake async" antipattern that leads to thread pool starvation and unnecessary context switching.
🚀 What you will learn:
1. Why "There is no thread" during true asynchronous I/O.
2. The hidden cost of Task.Run in a request-response lifecycle.
3. When Task.Run is actually the right choice (Parallel processing vs. Background tasks).
4. Best practices for keeping your Thread Pool healthy under high load.
👨💻 About this channel:
Learn Full Stack Development from scratch – Frontend, Backend, APIs, ASP.NET Core, Angular, React, SQL, Entity Framework, Clean Architecture & more.
📝 Helpful Links:
• Visit our website: https://f2bstack.com
• Subscribe: / @frontendtobackendwithrohan
• LinkedIn: / rohankumawat
• Github: https://github.com/rrohankumawat
• Instagram: / f2bstack
• X: https://x.com/f2bwithrohan
#dotnet #csharp #aspnetcore #webapi #programming #softwareengineering
Доступные форматы для скачивания:
Скачать видео mp4
-
Информация по загрузке:
