csharp-concurrency-patterns

Channels are the optimal .NET concurrency pattern for producer/consumer queues, providing safe backpressure and state isolation. This skill helps you apply decision trees to identify when channels outperform standard async/await workflows.

To prevent deadlocks and race conditions in async/await code, you must reduce shared mutable state and apply safe isolation patterns. This skill defines rules and examples that enforce safe concurrent execution across I/O-bound tasks.

You should use Akka.NET actors instead of async/await when managing stateful entities that require strict isolation and message-driven concurrency. This skill guides the selection of actors to balance scalability and maintainability in complex .NET applications.

Reactive Extensions (Rx) works well for handling streaming data in .NET by modeling asynchronous data streams with observable sequences. This skill helps determine when Rx is the right choice compared to channels and async/await.

Choosing between channels and Rx depends on whether your workflow needs producer/consumer backpressure or reactive stream transformations. This skill provides patterns to evaluate your specific I/O-bound tasks and select the appropriate abstraction.

Yes, you can apply these concurrency patterns to existing dotnet projects to refactor away from excessive locking. The skill provides real-world examples and best practices to migrate towards scalable and maintainable concurrent code.