csharp-concurrency-patterns

Optimal .NET concurrency depends on workload type: use async/await for IO-bound tasks and Channels or parallel processing for CPU-bound operations. This skill provides a decision tree to guide safe, scalable pattern selection across scenarios.

Choosing between async/await, Channels, and Akka.NET depends on workload complexity: start with async/await, escalate to Channels for producer/consumer streaming, and adopt Akka.NET Actors for stateful coordination. This skill offers level-based guidance and escalation paths.

Use .NET Channels instead of async/await when implementing producer/consumer or streaming scenarios requiring safe coordination without locks. This skill's decision tree identifies exactly when to escalate from basic async patterns to Channels.

Akka.NET works well for stateful concurrency coordination in dotnet by using the Actor model to avoid brittle synchronization. This skill provides escalation paths from basic patterns to Akka.NET Actors for complex stateful requirements.

Common async and concurrency anti-patterns in dotnet include using locks and brittle synchronization for state coordination. This skill outlines these anti-patterns and provides best practices to ensure safe, scalable concurrency decisions without deadlocks.

Your .NET concurrency implementation suffers from brittle synchronization due to improper lock usage. This skill helps you fix it by guiding tool selection from async/await to Channels and Akka.NET, ensuring safe coordination through a structured decision tree.