csharp-concurrency-patterns

For I/O-bound operations with backpressure, .NET Channels offer a robust producer/consumer pipeline solution that integrates seamlessly with async/await. This skill helps evaluate this pattern against alternatives to ensure scalable, non-blocking processing.

Choosing between async/await and Reactive Extensions (Rx) for stream processing depends on whether you need pull-based task coordination or push-based event streams. This skill provides decision guidance to compare their tradeoffs and select the correct abstraction for your scenario.

Use Akka.NET actors for stateful entity coordination when you need to encapsulate mutable state and message-passing, avoiding shared state locks. This skill outlines when actor-based concurrency is superior to standard parallel patterns for complex state management.

Common CPU-bound batch processing anti-patterns include overusing locks, blocking async operations, and relying on shared mutable state. This skill highlights these pitfalls and recommends safer parallel processing alternatives to maintain application throughput.

Yes, this concurrency decision framework explicitly supports producer/consumer pipelines built with .NET Channels. It evaluates when to apply Channels for I/O-bound workflows and how they compare to other concurrency abstractions for scalable data flow.