2. Real-world story

At HDFC net banking transfer service, engineers use Cancellation Tokens to keep APIs responsive while waiting for database and HTTP calls. This code shows the same pattern you will see in code reviews — simplified for learning, but structurally similar to production services deployed to Azure or on-prem IIS/Kestrel.

3. Problem without this concept

If you ignore Cancellation Tokens, this is what teams struggle with:

• Blocked threads under load → API timeouts
• Using .Result → random deadlocks

4. Definition

Cancellation Tokens is a core part of C# and .NET development. In plain terms: it helps you keep APIs responsive while waiting for database and HTTP calls.

5. Why do we need it?

You will see Cancellation Tokens in console apps, Web APIs, background workers, and unit tests. Skipping it makes later modules (OOP, async, collections) much harder. For Web APIs, mobile backends, and any I/O-bound work — default in ASP.NET Core.

6. Where is it used?

• ASP.NET Core Web APIs
• Mobile backends
• Microservice HTTP calls
• async/await keeps ASP.NET Core threads free while waiting for SQL and HTTP.
• Always pass CancellationToken in production API methods.

7. How it works

• Read the example top to bottom.
• Each line connects to Cancellation Tokens.
• Run it with dotnet run, then change one value and predict the output before you save.

8. Syntax

Core syntax pattern for Cancellation Tokens:

public async Task<ResultType> MethodAsync()
{
    var data = await SomeIoAsync();
    return data;
}

9. Beginner example

Copy into a console project (dotnet new console → dotnet run).

public static async Task<decimal> FetchBalanceAsync(string accountId)
{
    await Task.Delay(100); // simulates HTTP/DB
    return 12500.75m;
}

decimal balance = await FetchBalanceAsync("ACC-42");
Console.WriteLine($"Balance: ₹{balance:N2}");

Line-by-line

10. Real project example

At HDFC net banking transfer service, engineers use Cancellation Tokens to keep APIs responsive while waiting for database and HTTP calls. This code shows the same pattern you will see in code reviews — simplified for learning, but structurally similar to production services deployed to Azure or on-prem IIS/Kestrel.

Production-style C#

// HDFC net banking transfer service — Cancellation Tokens in production
public class PaymentClient
{
    private readonly HttpClient _http;

    public PaymentClient(HttpClient http) => _http = http;

    public async Task<PaymentResult> ChargeAsync(decimal amount, CancellationToken ct = default)
    {
        var response = await _http.PostAsJsonAsync("/api/payments", new { amount }, ct);
        response.EnsureSuccessStatusCode();
        return await response.Content.ReadFromJsonAsync<PaymentResult>(ct)
            ?? throw new InvalidOperationException("Empty response");
    }
}

public record PaymentResult(string TransactionId, bool Success);

Why teams use this: Teams that master Cancellation Tokens ship fewer production incidents and pass code review faster on HDFC-scale systems.

11. Visual understanding

Browser / Mobile app
        │
        ▼ HTTP request
   ASP.NET Core API  ──await──▶  Database / Payment API
        │
        ▼ JSON response
      Client UI updates

12. Internal working

• async method returns Task immediately; work continues when await completes.
• Thread pool threads are not blocked during I/O waits.
• State machine generated by compiler resumes after await.
• ASP.NET Core can handle more concurrent requests with async controllers.

13. Advantages

• Scales Web APIs without thousands of blocked threads
• Natural fit for database and HTTP I/O
• Standard pattern in ASP.NET Core since day one

14. Disadvantages

• async all the way through call stack — async void is a trap
• Debugging timing issues is harder than serial code

15. Best practices

• Always pass CancellationToken in APIs
• Never block with .Result on ASP.NET threads
• Use `ConfigureAwait(false)` in library code

16. Common mistakes

• Copy-pasting without typing — your fingers need to remember Cancellation Tokens syntax.
• Skipping error messages when the compiler fails — the red text usually tells you exactly what to fix.

17. Interview questions

Do this on your computer

1. Open Visual Studio or run dotnet new console -n LearnCancellation.
2. Paste the lesson example into Program.cs (or a new file).
3. Run the program and confirm the output matches your expectation.
4. Read the real-world section and name which part of a banking or e-commerce API would use this topic.
5. Change one line (amount, loop bound, or method name) and run again.
6. Read the real-world section and identify which layer (API, service, domain) uses this topic.
7. Run dotnet build and dotnet run locally — confirm output.
8. Change one value and predict the result before saving.

Experiments — try changing this

• Change a number or string in the example and run again — predict output first.
• Introduce a deliberate error (remove a semicolon) and read the compiler message.
• Add Task.Delay and see how await keeps the method non-blocking.
• Open dotnet docs for Cancellation Tokens and compare one keyword with the lesson example.

18. Summary

• Cancellation Tokens is used to keep APIs responsive while waiting for database and HTTP calls.
• Practice by editing the example yourself.
• Move to the next lesson when you can explain this topic in your own words.