Does this skill cover UI-specific concurrency?

Yes, it includes specialized guidance on using Reactive Extensions (Rx) for UI event handling, debouncing, and throttling in frameworks like WPF, Blazor, and MAUI.

What is the recommended default for concurrency in .NET?

The skill follows the 'start simple' rule, recommending async/await as the default choice for I/O-bound operations and escalating to more complex tools only when necessary.

When should I use the .NET Concurrency Patterns skill?

Use this skill whenever you are designing concurrent systems in .NET and need to decide between different abstractions like async/await, Channels, Actors, or Reactive Extensions.

How does this skill handle thread safety?

It promotes a philosophy of avoiding shared mutable state through immutability, message passing, and actor isolation rather than relying on manual locks or semaphores.

.NET Concurrency Patterns

Name: .NET Concurrency Patterns
Author: Aaronontheweb

byAaronontheweb

•

203

API Development

Guides .NET developers in selecting and implementing optimal concurrency abstractions from async/await to Akka.NET actor models.

About

The .NET Concurrency Patterns skill provides a structured architectural framework for managing asynchronous and parallel operations in C#. It helps developers move away from error-prone manual locks and synchronization primitives by advocating for a progressive complexity model. By following a built-in decision tree, users can determine when to use simple async/await for I/O, System.Threading.Channels for work queues, or Akka.NET for complex stateful entities and backpressured streams, ensuring high-performance and maintainable codebases.

Key Features

Producer-consumer patterns using System.Threading.Channels
203 GitHub stars
Advanced stream processing and actor model guidance via Akka.NET
Comprehensive decision tree for selecting the right concurrency tool
Best practices for async/await and non-blocking I/O implementation
Reactive Extensions (Rx) patterns for UI event composition and debouncing

Use Cases

Refactoring legacy codebases to remove manual locks and thread-safety bugs
Evaluating the best architectural approach for a high-throughput data pipeline
Implementing complex state machines with independent, concurrent entities

About

Key Features

Producer-consumer patterns using System.Threading.Channels
203 GitHub stars
Advanced stream processing and actor model guidance via Akka.NET
Comprehensive decision tree for selecting the right concurrency tool
Best practices for async/await and non-blocking I/O implementation
Reactive Extensions (Rx) patterns for UI event composition and debouncing

Use Cases

Refactoring legacy codebases to remove manual locks and thread-safety bugs
Evaluating the best architectural approach for a high-throughput data pipeline
Implementing complex state machines with independent, concurrent entities