csharp-messaging

What problem does it solve?

Provides clear, graduated guidance for selecting and implementing messaging and middleware patterns in C# applications so teams pick the right solution for scale, durability, and operational needs. It reduces costly architecture mistakes by mapping trade-offs between in-process channels, MediatR, brokered transports, streaming platforms, and enterprise service buses.

Core Features & Use Cases

• Graduated decision matrix: from System.Threading.Channels for in-process work to NServiceBus for enterprise sagas.
• Transport-specific examples: runnable patterns and wiring for MediatR, MassTransit+RabbitMQ, Azure Service Bus, Confluent.Kafka, and NServiceBus.
• Reliability & operations: guidance on retries, idempotency, dead-letter handling, outbox patterns, and backpressure strategies.
• Use Case: design an order processing pipeline that starts with Channels+MediatR for a single service and migrates to MassTransit+RabbitMQ or Kafka as throughput and cross-service needs grow.

Quick Start

Help me design an order processing pipeline in C#: recommend the appropriate messaging pattern for my scale, explain trade-offs, and show minimal producer and consumer code for the selected transport.