#messaging

  • Claim Check Pattern
    Explains how to move large payloads out of a messaging system by storing them externally and sending only a claim-check token, with Azure Blob Storage and Service Bus examples.
  • Competing Consumers Pattern
    Explains how multiple consumers can process messages from a single queue concurrently to improve throughput, scalability, and availability, including poison-message and idempotency concerns.
  • Messaging Bridge Pattern
    Explains building a bridge component that relays messages between incompatible messaging infrastructures, such as MSMQ and Azure Service Bus, without changing existing systems.
  • Pipes And Filters Pattern
    Decompose a complex processing task into a chain of reusable, independently deployable and scalable filters connected by pipes.
  • Priority Queue Pattern
    Let a system process high-priority requests ahead of low-priority ones, using a priority-aware queue or separate queues per priority level.
  • Publisher Subscriber Pattern
    Announce events to many interested consumers asynchronously through a message broker, without tightly coupling senders to receivers.
  • Queue Based Load Leveling Pattern
    Place a queue between a task and the service it calls so the queue buffers intermittent heavy loads and smooths out peak demand.
  • Sequential Convoy Pattern
    Process related messages in a defined order without blocking other message groups, using categories and message sessions to keep FIFO while scaling out.