Task and Async/Await — Non-Blocking Asynchronous Code

Asynchronous programming with async/await is the cornerstone of ASP.NET Core’s scalability. Every database call, HTTP request, file operation, and external API call should be asynchronous. The reason: ASP.NET Core serves requests using a thread pool. When a thread blocks waiting for I/O, it cannot serve other requests. With async/await, the thread is released back to the pool while the I/O completes, allowing it to handle hundreds of other requests. A server that blocks threads can handle dozens of concurrent requests; the same server with async I/O can handle thousands.

Task and Async/Await Fundamentals #

// ── Synchronous — blocks the thread while waiting ────────────────────────
string SyncGetPost(int id)
{
    Thread.Sleep(500);           // blocks the thread for 500ms
    return $"Post {id}";
}

// ── Asynchronous — releases the thread while waiting ─────────────────────
async Task<string> AsyncGetPost(int id)
{
    await Task.Delay(500);       // releases the thread; resumes after 500ms
    return $"Post {id}";
}

// ── Calling async methods ─────────────────────────────────────────────────
// In an async method: use await
string post = await AsyncGetPost(42);
Console.WriteLine(post);   // "Post 42"

// Async method returning void return type — use Task
async Task DoWorkAsync()
{
    var post = await AsyncGetPost(1);
    Console.WriteLine(post);
}

// Async method returning a value — use Task<T>
async Task<Post> GetByIdAsync(int id, CancellationToken ct = default)
{
    var post = await _db.Posts.FindAsync(new object[] { id }, ct);
    return post ?? throw new NotFoundException(nameof(Post), id);
}

What the Compiler Generates #

// This async method:
async Task<int> GetCountAsync()
{
    await Task.Delay(100);
    return 42;
}

// Compiles to roughly this (simplified state machine):
// class GetCountAsyncStateMachine : IAsyncStateMachine
// {
//     int _state = -1;
//     TaskCompletionSource<int> _tcs = new();
//
//     void MoveNext()
//     {
//         if (_state == 0) goto resume;
//         var awaiter = Task.Delay(100).GetAwaiter();
//         if (!awaiter.IsCompleted) { _state = 0; awaiter.OnCompleted(MoveNext); return; }
//         resume:
//         _tcs.SetResult(42);
//     }
// }
// The key insight: no thread is blocked during Task.Delay — the thread pool is
// freed and MoveNext() is called again when the delay completes.

Async Return Types #

Common Mistakes #

Mistake 1 — Blocking on async code with .Result or .Wait() (deadlock risk) #

❌ Wrong — can deadlock in UI/ASP.NET Framework contexts:

var post = GetByIdAsync(42).Result;   // blocks + potential deadlock!

✅ Correct — await all the way up:

var post = await GetByIdAsync(42);   // ✓ non-blocking

Mistake 2 — Forgetting await (task is not observed) #

❌ Wrong — the task runs but its result/exception is not observed:

_service.SendEmailAsync(user.Email);   // no await — exception disappears!

✅ Correct:

await _service.SendEmailAsync(user.Email);   // ✓