When to use asynchronous tasks in asp.net core mvc?

Question

Can you give practical scenario and explain why we need to use asynchronous tasks there?

Answer 1

Please see the documentation below for more of an explanation:

https://learn.microsoft.com/en-us/aspnet/mvc/overview/performance/using-asynchronous-methods-in-aspnet-mvc-4

Also here is an example from C# to help you understand from a real-life example:

https://learn.microsoft.com/en-us/dotnet/csharp/async

Answer 2

following the node model, to gain perform asp.net core decided to use a limited number of request pipeline threads (cpu count) and depend on async processing to allow the same thread to process multiple requests concurrently.

if you need scaling (large number of concurrent requests), then you need to use async for all network, database, file, and any long computing tasks. that is is an api supports an async version, you should use the async version. if you don't, your site will run fine, it just will not scale up to a large number of requests.

Answer 3

When to use asynchronous tasks in asp.net core mvc?

Can the following Microsoft documents help?

Async Programming : Introduction to Async/Await on ASP.NET
https://learn.microsoft.com/en-us/archive/msdn-magazine/2014/october/async-programming-introduction-to-async-await-on-asp-net

ASP.NET Core Performance Best Practices
https://learn.microsoft.com/en-us/aspnet/core/performance/performance-best-practices?view=aspnetcore-6.0