Azure Service Bus: Messaging Patterns

On this page

Service Bus is Azure’s fully managed enterprise message broker. It supports Queues (point-to-point) and Topics/Subscriptions (pub/sub). Choosing the right pattern prevents architectural headaches.

Queues vs Topics

graph LR
    subgraph Queue
        Sender1[Sender] --> Q[Queue]
        Q --> Receiver1[Receiver]
    end
    
    subgraph TopicSub ["Topic & Subscriptions"]
        Publisher[Publisher] --> Topic[Topic]
        Topic --> SubA[Subscription A]
        Topic --> SubB[Subscription B]
    end
    
    style Topic fill:#E1F5FE

Dead-Letter Queue

Messages that fail processing N times go to a special DLQ for inspection and replay.

Key Takeaways

  • Use **Sessions** for ordered processing (FIFO for a specific session ID).
  • Use **Duplicate Detection** if your senders might retry.

Discover more from C4: Container, Code, Cloud & Context

Subscribe to get the latest posts sent to your email.

Written by

Nithin Mohan TK

Hello Namaste! 👋🏻 I'm an accomplished Enterprise Solution Architect & Engineering Leader with 20+ years of progressive experience architecting, building, and scaling transformative enterprise solutions. ⚜️ Solution Architect / AI & Cloud 📌 Galway, Ireland

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.