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。

查看原文