Queues and Background Tasks in C#: How to Speed Up Your App Without Pain

Why Your C# Application Needs Queues and Background Tasks?

Imagine: you launch a web application in C#, a user clicks the "Send Report" button, and... the server freezes for 30 seconds while generating a PDF. Sound familiar? In 2024, users don't tolerate lag. The solution is queues and background tasks. They turn synchronous hell into asynchronous heaven.

In this article, we'll break down how to properly organize background processing in C#: from built-in Channel<T> to industrial-grade RabbitMQ. You'll learn how to offload heavy work from the main thread without breaking the architecture. Let's go!

What is a Task Queue and Why Do You Need It in C#?

A queue is a FIFO (First In, First Out) data structure. In the context of C#, it's a mechanism that allows you to defer task execution so as not to block the main thread. A background task is code that runs "behind the scenes" while the user continues clicking around the site.

Typical scenarios:

\n
• Sending email notifications (100 emails = 100 requests to SMTP)
\n
• Generating reports and Excel files
\n
• Processing uploaded images (resize, watermark)
\n
• Integration with external APIs (slow responses)
\n
• Logging to a database (to avoid slowing down the UI)
\n

Without queues, a C# application will "hang" on every heavy request. With queues, you simply put the task in a buffer and respond to the user: "Done, we are processing it."

Option 1: Background Tasks via BackgroundService (Built-in .NET)

The simplest way is to use BackgroundService from Microsoft.Extensions.Hosting. This is a base class for creating background services in ASP.NET Core. It's perfect for simple scenarios where complex message routing isn't needed.

Example: Background Handler with Channel<T>

Let's write a simple Producer-Consumer. The Producer (controller) puts a task into the channel, and the Consumer (BackgroundService) picks it up and executes it.

// Step 1. Create a channel (thread-safe queue)\npublic class TaskChannel\n{\n    private readonly Channel<string> _channel = \n        Channel.CreateBounded<string>(new BoundedChannelOptions(100)\n        {\n            FullMode = BoundedChannelFullMode.Wait\n        });\n\n    public ChannelWriter<string> Writer => _channel.Writer;\n    public ChannelReader<string> Reader => _channel.Reader;\n}\n\n// Step 2. BackgroundService that reads from the channel\npublic class EmailBackgroundService : BackgroundService\n{\n    private readonly TaskChannel _taskChannel;\n\n    public EmailBackgroundService(TaskChannel taskChannel)\n    {\n        _taskChannel = taskChannel;\n    }\n\n    protected override async Task ExecuteAsync(CancellationToken stoppingToken)\n    {\n        await foreach (var emailData in _taskChannel.Reader.ReadAllAsync(stoppingToken))\n        {\n            // Simulate sending an email (2 seconds)\n            await Task.Delay(2000, stoppingToken);\n            Console.WriteLine($"Email sent: {emailData}");\n        }\n    }\n}\n\n// Step 3. Controller that puts tasks\n[ApiController]\n[Route("api/email")]\npublic class EmailController : ControllerBase\n{\n    private readonly TaskChannel _taskChannel;\n\n    public EmailController(TaskChannel taskChannel)\n    {\n        _taskChannel = taskChannel;\n    }\n\n    [HttpPost("send")]\n    public IActionResult SendEmail([FromBody] string emailData)\n    {\n        _taskChannel.Writer.TryWrite(emailData);\n        return Accepted(new { message = "Email queued" });\n    }\n}\n\n// Step 4. Registration in Program.cs\nbuilder.Services.AddSingleton<TaskChannel>();\nbuilder.Services.AddHostedService<EmailBackgroundService>();

What's happening here? The user calls POST /api/email/send — the data goes into the ch