What are the advantages and disadvantages of using Task.Run inside an ASP.NET Core controller for executing tasks?

Using Task.Run inside an ASP.NET Core controller has the following advantages and disadvantages:

Advantages:

• Allows executing CPU-bound tasks asynchronously without blocking the request thread.
• Can help avoid blocking the main thread when performing heavy computations.

Disadvantages:

• ASP.NET Core is already built on an asynchronous model, and for I/O-bound operations, it's better to use async/await without Task.Run.
• Task.Run runs the task on a thread pool, which can lead to excessive context switching and reduced performance.
• If the task depends on the request context (e.g., HttpContext), this context may be unavailable when running in Task.Run.
• It can lead to unexpected errors and complicate debugging.

Conclusion: Task.Run should only be used in controllers for CPU-intensive operations that cannot be made asynchronous otherwise. For I/O operations, it's preferable to use async/await directly.

public async Task<IActionResult> GetData()
{
    // Bad: launching I/O operation via Task.Run
    var data = await Task.Run(() => GetDataFromDb());

    // Better: use the asynchronous method directly
    var dataAsync = await GetDataFromDbAsync();

    return Ok(dataAsync);
}