csharp-concurrency-patterns

To prevent concurrency bugs, avoid common anti-patterns like blocking on async code or using locks inappropriately. Instead, use synchronization primitives like SemaphoreSlim, Interlocked, and concurrent collections correctly.

Use Channels in C# for high-throughput producer/consumer work queues. Choose Akka.NET actors instead when you need complex stateful entity management and a clear escalation path for concurrent scenarios.

The best way to process concurrent requests without blocking in .NET is using async/await for I/O operations or Channels for work queues. Parallel.ForEachAsync is suitable for CPU-bound parallel processing tasks.

SemaphoreSlim differs from the lock statement by supporting asynchronous waiting, making it suitable for async/await code. Use lock for quick in-memory synchronization and Interlocked for atomic operations on simple types.

Blocking on async code causes problems like deadlocks and thread pool starvation. This anti-pattern defeats the purpose of async/await concurrency, preventing efficient resource utilization and degrading application performance.