csharp-concurrency-patterns

SKILL.md

Most concurrency problems can be solved with async/await. Only reach for more sophisticated tools when you have a specific need that async/await can't address cleanly.

Try to avoid shared mutable state. The best way to handle concurrency is to design it away. Immutable data, message passing, and isolated state (like actors) eliminate entire categories of bugs.

Locks should be the exception, not the rule. When you can't avoid shared mutable state, using a lock occasionally isn't the end of the world. But if you find yourself reaching for lock, SemaphoreSlim, or other synchronization primitives regularly, step back and reconsider your design.

在 .NET 中选择正确的并发抽象 - 从 I/O 的异步/等待到生产者/消费者的通道，再到用于状态实体管理的 Akka.NET。除非绝对必要，否则避免锁定和手动同步。 来源：aaronontheweb/dotnet-skills。

查看原文