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.

Choisir la bonne abstraction de concurrence dans .NET - de l'asynchrone/attente des E/S aux canaux pour le producteur/consommateur en passant par Akka.NET pour la gestion des entités avec état. Évitez les verrouillages et la synchronisation manuelle, sauf en cas d'absolue nécessité. Source : aaronontheweb/dotnet-skills.

Voir l'original