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를 위한 async/await부터 생산자/소비자를 위한 채널, 상태 저장 엔터티 관리를 위한 Akka.NET까지. 꼭 필요한 경우가 아니면 잠금 및 수동 동기화를 피하세요. 출처: aaronontheweb/dotnet-skills.

원본 보기