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.

I/O の async/await からプロデューサー/コンシューマーのチャネル、ステートフル エンティティ管理の Akka.NET まで、.NET での適切な同時実行抽象化の選択。どうしても必要な場合を除き、ロックや手動同期は避けてください。 ソース: aaronontheweb/dotnet-skills。

原文を見る