This document provides an overview of Windows Azure Service Bus and its key components: - Service Bus allows one-directional communication via queues that store messages until received and topics that use subscriptions to filter messages. It also enables bi-directional communication via relays. - Service Bus queues are used for communication between applications like web and worker roles or on-premises and cloud apps. - Topics and subscriptions provide one-to-many communication using a publish/subscribe pattern with optional filtering of messages for each subscription. - The Service Bus relay enables hybrid apps that run in Azure and on-premises without requiring firewall configuration changes.

1. Core Systems Transformation Solutions
Windows Azure Service Bus
Alexey Izyumov, .Net developer

2. Confidential 1
Agenda
• Service Bus Overview
• Namespace and Access Control
• Service Bus Queues
• Service Bus Topics

3. Confidential 2
Service Bus - Overview
Windows Azure Service Bus
Queue 1 Queue 2 RelayTopic 1 Topic 2
Publisher Service Web-site Mobile
• Queues – allow one-directional communication.
Each queue acts as an intermediary (sometimes called a broker) that stores sent messages until
they are received.
• Topics – provide one-directional communication using subscriptions.
Like a queue, a topic acts as a broker, but it allows each subscription to see only messages that
match specific criteria.
• Relays – provide bi-directional communication.
Unlike queues and topics, a relay doesn't store in-flight messages-it's not a broker. Instead, it
just passes them on to the destination application.

4. Confidential 3
What are Service Bus Queues?
• Communication between web and worker roles in a multi-tier Windows Azure application
• Communication between on-premises apps and Windows Azure hosted apps in a hybrid
solution
• Communication between components of a distributed application running on-premises in
different organizations or departments of an organization

5. Confidential 4
What are Service Bus Topics and Subscriptions?
• Topics and subscriptions provide a one-to-many form of communication, using a
publish/subscribe pattern
• A topic subscription resembles a virtual queue that receives copies of the messages that
were sent to the topic. You can optionally register filter rules for a topic on a per-
subscription basis, which allows you to filter/restrict which messages to a topic are
received by which topic subscriptions.
• Service Bus topics and subscriptions enable you to scale to process a very large number of
messages across a very large number of users and applications.

6. Confidential 5
What is the Service Bus Relay?
The Service Bus Relay service enables you to build hybrid applications that run
in both a Windows Azure datacenter and your own on-premises enterprise
environment, without having to open up a firewall connection or requiring
intrusive changes to a corporate network infrastructure.

7. Confidential 6
Service Bus Namespace
https://yourapp.servicebus.windows.net/foo/bar/baz

8. Confidential 7
Service Bus Rights and Claims

9. Confidential 8
Namespace and Access Control
DEMO

10. Confidential 9
Push vs. Pull

11. Confidential 10
Ways to Pull

12. Confidential 11
Messages

13. Confidential 12
Queues

14. Confidential 13
Queues

15. Confidential 14
Topics

16. Confidential 15
Runtime API Choices

17. Confidential 16
Service Bus Queues & Topics
DEMO

18. Confidential 17
Thank you
Q & A