Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Merge pull request #412 from mollybostic/weekly_1009

#400 -- updating service bus feature guides for 2.6
  • Loading branch information...
commit e33003146f5dceee01515839f0586cd82894ce1f 2 parents 422a75f + e4b529b
scottturnbull scottturnbull authored
88 DevCenter/Java/HowTo/service-bus-queues.md
Source Rendered
@@ -20,87 +20,7 @@ messages**, and **deleting queues**.
20 20 - [How to: Handle Application Crashes and Unreadable Messages][]
21 21 - [Next Steps][]
22 22
23   -## <a name="bkmk_WhatAreSvcBusQueues"> </a>What are Service Bus Queues?
24   -
25   -Service Bus Queues support a **brokered messaging communication** model.
26   -When using queues, components of a distributed application do not
27   -communicate directly with each other, they instead exchange messages via
28   -a queue, which acts as an intermediary. A message producer (sender)
29   -hands off a message to the queue and then continues its processing.
30   -Asynchronously, a message consumer (receiver) pulls the message from the
31   -queue and processes it. The producer does not have to wait for a reply
32   -from the consumer in order to continue to process and send further
33   -messages. Queues offer **First In, First Out (FIFO)** message delivery
34   -to one or more competing consumers. That is, messages are typically
35   -received and processed by the receivers in the order in which they were
36   -added to the queue, and each message is received and processed by only
37   -one message consumer.
38   -
39   -![Service Bus Queue Diagram][]
40   -
41   -Service Bus queues are a general-purpose technology that can be used for
42   -a wide variety of scenarios:
43   -
44   -- Communication between web and worker roles in a multi-tier Windows
45   - Azure application
46   -- Communication between on-premises apps and Windows Azure hosted apps
47   - in a hybrid solution
48   -- Communication between components of a distributed application
49   - running on-premises in different organizations or departments of an
50   - organization
51   -
52   -Using queues can enable you to scale out your applications better, and
53   -enable more resiliency to your architecture.
54   -
55   -## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
56   -
57   -To begin using Service Bus queues in Windows Azure, you must first
58   -create a service namespace. A service namespace provides a scoping
59   -container for addressing Service Bus resources within your application.
60   -
61   -To create a service namespace:
62   -
63   -1. Log on to the [Windows Azure Management Portal][].
64   -2. In the lower left navigation pane of the Management Portal, click
65   - **Service Bus, Access Control & Caching**.
66   -3. In the upper left pane of the Management Portal, click the **Service
67   - Bus** node, and then click the **New** button.
68   - ![Service Bus Node screenshot][]
69   -4. In the **Create a new Service Namespace** dialog, enter a
70   - **Namespace**, and then to make sure that it is unique, click the
71   - **Check Availability** button.
72   - ![Create a New Namespace screenshot][]
73   -5. After making sure the namespace name is available, choose the
74   - country or region in which your namespace should be hosted (make
75   - sure you use the same country/region in which you are deploying your
76   - compute resources), and then click the **Create Namespace** button.
77   - Having a compute instance is optional, and the service bus can be
78   - consumed from any application with internet access.
79   -
80   - The namespace you created will then appear in the Management Portal
81   - and takes a moment to activate. Wait until the status is **Active**
82   - before moving on.
83   -
84   -## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
85   -
86   -In order to perform management operations, such as creating a queue, on
87   -the new namespace, you need to obtain the management credentials for the
88   -namespace.
89   -
90   -1. In the left navigation pane, click the **Service Bus** node, to
91   - display the list of available namespaces:
92   - ![Available Namespaces screenshot][]
93   -2. Select the namespace you just created from the list shown:
94   - ![Namespace List screenshot][]
95   -3. The right-hand **Properties** pane will list the properties for the
96   - new namespace:
97   - ![Properties Pane screenshot][]
98   -4. The **Default Key** is hidden. Click the **View** button to display
99   - the security credentials:
100   - ![Default Key screenshot][]
101   -5. Make a note of the **Default Issuer** and the **Default Key** as you
102   - will use this information below to perform operations with the
103   - namespace.
  23 +<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
104 24
105 25 ## <a name="bkmk_ConfigApp"> </a>Configure Your Application to Use Service Bus
106 26
@@ -320,9 +240,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
320 240 topic [Queues, Topics, and Subscriptions][] for more information.
321 241
322 242 [Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
323   - [What are Service Bus Queues?]: #bkmk_WhatAreSvcBusQueues
324   - [Create a Service Namespace]: #bkmk_CreateSvcNamespace
325   - [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
  243 + [What are Service Bus Queues?]: #what-are-service-bus-queues
  244 + [Create a Service Namespace]: #create-a-service-namespace
  245 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
326 246 [Configure Your Application to Use Service Bus]: #bkmk_ConfigApp
327 247 [How to: Create a Security Token Provider]: #bkmk_HowToCreateQueue
328 248 [How to: Send Messages to a Queue]: #bkmk_HowToSendMsgs
82 DevCenter/Java/HowTo/service-bus-topics.md
Source Rendered
@@ -22,81 +22,7 @@ messages to a topic**, **receiving messages from a subscription**, and
22 22 - [How to: Delete Topics and Subscriptions][]
23 23 - [Next Steps][]
24 24
25   -## <a name="bkmk_WhatAreSvcBusTopics"> </a>What are Service Bus Topics and Subscriptions?
26   -
27   -Service Bus topics and subscriptions support a **publish/subscribe
28   -messaging communication** model. When using topics and subscriptions,
29   -components of a distributed application do not communicate directly with
30   -each other, they instead exchange messages via a topic, which acts as an
31   -intermediary.
32   -![Service Bus Topics diagram][]
33   -
34   -In contrast to Service Bus queues, where each message is processed by a
35   -single consumer, topics and subscriptions provide a **one-to-many** form
36   -of communication, using a publish/subscribe pattern. It is possible to
37   -register multiple subscriptions to a topic. When a message is sent to a
38   -topic, it is then made available to each subscription to handle/process
39   -independently.
40   -
41   -A topic subscription resembles a virtual queue that receives copies of
42   -the messages that were sent to the topic. You can optionally register
43   -filter rules for a topic on a per-subscription basis, which allows you
44   -to filter/restrict which messages to a topic are received by which topic
45   -subscriptions.
46   -
47   -Service Bus topics and subscriptions enable you to scale to process a
48   -very large number of messages across a very large number of users and
49   -applications.
50   -
51   -## <a name="bkmk_CreateSvcNamespace"> </a>Create a Service Namespace
52   -
53   -To begin using Service Bus topics in Windows Azure, you must first
54   -create a service namespace. A service namespace provides a scoping
55   -container for addressing Service Bus resources within your application.
56   -
57   -**To create a service namespace:**
58   -
59   -1. Log on to the [Windows Azure Management Portal][].
60   -2. In the lower left navigation pane of the Management Portal, click
61   - **Service Bus, Access Control & Caching**.
62   -3. In the upper left pane of the Management Portal, click the **Service
63   - Bus** node, and then click the **New** button.
64   - ![Service Bus Node screenshot][]
65   -4. In the **Create a new Service Namespace** dialog, enter a
66   - **Namespace**, and then to make sure that it is unique, click the
67   - **Check Availability** button.
68   - ![Create a New Namespace ][]
69   -5. After making sure the namespace name is available, choose the
70   - country or region in which your namespace should be hosted (make
71   - sure you use the same country/region in which you are deploying your
72   - compute resources), and then click the **Create Namespace** button.
73   - Having a compute instance is optional, and the service bus can be
74   - consumed from any application with internet access.
75   -
76   - The namespace you created will then appear in the Management Portal
77   - and takes a moment to activate. Wait until the status is **Active**
78   - before moving on.
79   -
80   -## <a name="bkmk_ObtainDefaultMngmntCredentials"> </a>Obtain the Default Management Credentials for the Namespace
81   -
82   -In order to perform management operations, such as creating a topic, on
83   -the new namespace, you need to obtain the management credentials for the
84   -namespace.
85   -
86   -1. In the left navigation pane, click the **Service Bus** node, to
87   - display the list of available namespaces:
88   - ![Available Namespaces ][Service Bus Node screenshot]
89   -2. Select the namespace you just created from the list shown:
90   - ![Namespace List screenshot][]
91   -3. The right-hand **Properties** pane will list the properties for the
92   - new namespace:
93   - ![Properties Pane screenshot][]
94   -4. The **Default Key** is hidden. Click the **View** button to display
95   - the security credentials:
96   - ![Default Key screenshot][]
97   -5. Make a note of the **Default Issuer** and the **Default Key** as you
98   - will use this information below to perform operations with the
99   - namespace.
  25 +<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
100 26
101 27 ## <a name="bkmk_ConfigYourApp"> </a>Configure Your Application to Use Service Bus
102 28
@@ -409,9 +335,9 @@ Now that you've learned the basics of Service Bus queues, see the MSDN
409 335 topic [Queues, Topics, and Subscriptions][] for more information.
410 336
411 337 [Windows Azure SDK for Java]: http://msdn.microsoft.com/en-us/library/windowsazure/hh690953(v=vs.103).aspx
412   - [What are Service Bus Topics and Subscriptions?]: #bkmk_WhatAreSvcBusTopics
413   - [Create a Service Namespace]: #bkmk_CreateSvcNamespace
414   - [Obtain the Default Management Credentials for the Namespace]: #bkmk_ObtainDefaultMngmntCredentials
  338 + [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
  339 + [Create a Service Namespace]: #create-a-service-namespace
  340 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
415 341 [Configure Your Application to Use Service Bus]: #bkmk_ConfigYourApp
416 342 [How to: Create a Topic]: #bkmk_HowToCreateTopic
417 343 [How to: Create Subscriptions]: #bkmk_HowToCreateSubscrip
105 DevCenter/Node/HowTo/service-bus-queues.md
Source Rendered
... ... @@ -1,4 +1,4 @@
1   -<properties linkid="dev-nodejs-how-to-service-bus-queues" urldisplayname="Service Bus Queues" headerexpose="" pagetitle="Service Bus Queues - How To - Node.js - Develop" metakeywords="Azure messaging, Azure brokered messaging, Azure messaging queue, Service Bus queue, Azure Service Bus queue, Azure messaging Node.js, Azure messaging queue Node.js, Azure Service Bus queue Node.js, Service Bus queue Node.js" footerexpose="" metadescription="Learn about Windows Azure Service Bus queues, including how to create queues, how to send and receive messages, and how to delete queues." umbraconavihide="0" disquscomments="1"></properties>
  1 +<properties linkid="dev-nodejs-how-to-service-bus-queues" urldisplayname="Service Bus Queues" headerexpose="" pagetitle="Service Bus Queues - How To - Node.js - Develop" metakeywords="Azure messaging, Azure brokered messaging, Azure messaging queue, Service Bus queue, Azure Service Bus queue, Azure messaging Node.js, Azure messaging queue Node.js, Azure Service Bus queue Node.js, Service Bus queue Node.js" footerexpose="" metadescription="Learn about Windows Azure Service Bus queues, including how to create queues, how to send and receive messages, and how to delete queues." umbraconavihide="0" disquscomments="1"></properties>
2 2
3 3 # How to Use Service Bus Queues
4 4
@@ -10,7 +10,7 @@ Steps] section.
10 10
11 11 ## Table of Contents
12 12
13   -- [What are Service Bus Queues][]
  13 +- [What are Service Bus Queues?][]
14 14 - [Create a Service Namespace][]
15 15 - [Obtain the Default Management Credentials for the Namespace][]
16 16 - [Create a Node.js Application][]
@@ -21,100 +21,7 @@ Steps] section.
21 21 - [How to: Handle Application Crashes and Unreadable Messages][]
22 22 - [Next Steps][]
23 23
24   -## <a name="what-queues"> </a>What are Service Bus Queues
25   -
26   -Service Bus Queues support a **brokered messaging communication** model.
27   -When using queues, components of a distributed application do not
28   -communicate directly with each other, they instead exchange messages via
29   -a queue, which acts as an intermediary. A message producer (sender)
30   -hands off a message to the queue and then continues its processing.
31   -Asynchronously, a message consumer (receiver) pulls the message from the
32   -queue and processes it. The producer does not have to wait for a reply
33   -from the consumer in order to continue to process and send further
34   -messages. Queues offer **First In, First Out (FIFO)** message delivery
35   -to one or more competing consumers. That is, messages are typically
36   -received and processed by the receivers in the order in which they were
37   -added to the queue, and each message is received and processed by only
38   -one message consumer.
39   -
40   -![Queue Concepts][]
41   -
42   -Service Bus queues are a general-purpose technology that can be used for
43   -a wide variety of scenarios:
44   -
45   -- Communication between web and worker roles in a multi-tier Windows
46   - Azure application
47   -- Communication between on-premises apps and Windows Azure hosted apps
48   - in a hybrid solution
49   -- Communication between components of a distributed application
50   - running on-premises in different organizations or departments of an
51   - organization
52   -
53   -Using queues can enable you to scale out your applications better, and
54   -enable more resiliency to your architecture.
55   -
56   -## <a name="create-namespace"> </a>Create a Service Namespace
57   -
58   -To begin using Service Bus queues in Windows Azure, you must first
59   -create a service namespace. A service namespace provides a scoping
60   -container for addressing Service Bus resources within your application.
61   -
62   -To create a service namespace:
63   -
64   -1. Log on to the [Windows Azure Management Portal][]. In order to perform the following steps you must use the Production portal. If you are currently using the Preview portal, you can switch to Production by clicking **Preview** at the top of the page, and then selecting **Take me to the previous portal**. This will load the production management portal.
65   -
66   - ![preview portal dialog][Previous Management Portal]
67   -
68   -2. In the lower left navigation pane of the Management Portal, click
69   - **Service Bus, Access Control & Caching**.
70   -
71   -3. In the upper left pane of the Management Portal, click the **Service
72   - Bus** node, and then click the **New** button.
73   -
74   - ![image][]
75   -
76   -4. In the **Create a new Service Namespace** dialog, enter a
77   - **Namespace**, and then to make sure that it is unique, click the
78   - **Check Availability** button.
79   -
80   - ![image][1]
81   -
82   -5. After making sure the namespace name is available, choose the
83   - country or region in which your namespace should be hosted (make
84   - sure you use the same country/region in which you are deploying your
85   - compute resources), and then click the **Create Namespace** button.
86   -
87   -The namespace you created will then appear in the Management Portal and
88   -takes a moment to activate. Wait until the status is **Active** before
89   -moving on.
90   -
91   -## <a name="obtain-creds"> </a>Obtain the Default Management Credentials for the Namespace
92   -
93   -In order to perform management operations, such as creating a queue, on
94   -the new namespace, you need to obtain the management credentials for the
95   -namespace.
96   -
97   -1. In the left navigation pane, click the **Service Bus** node, to
98   - display the list of available namespaces:
99   -
100   - ![image][]
101   -
102   -2. Select the namespace you just created from the list shown:
103   -
104   - ![image][2]
105   -
106   -3. The right-hand **Properties** pane will list the properties for the
107   - new namespace:
108   -
109   - ![image][3]
110   -
111   -4. The **Default Key** is hidden. Click the **View** button to display
112   - the security credentials:
113   -
114   - ![image][4]
115   -
116   -5. Make a note of the **Default Key** as you will use this information
117   - below to perform operations with the namespace.
  24 +<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
118 25
119 26 ## <a name="create-app"> </a>Create a Node.js Appication
120 27
@@ -332,9 +239,9 @@ links to learn more.
332 239
333 240 [Azure SDK for Node]: https://github.com/WindowsAzure/azure-sdk-for-node
334 241 [Next Steps]: #next-steps
335   - [What are Service Bus Queues]: #what-queues
336   - [Create a Service Namespace]: #create-namespace
337   - [Obtain the Default Management Credentials for the Namespace]: #obtain-creds
  242 + [What are Service Bus Queues?]: #what-are-service-bus-queues
  243 + [Create a Service Namespace]: #create-a-service-namespace
  244 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
338 245 [Create a Node.js Application]: #create-app
339 246 [Configure Your Application to Use Service Bus]: #configure-app
340 247 [How to: Create a Queue]: #create-queue
103 DevCenter/Node/HowTo/service-bus-topics.md
Source Rendered
... ... @@ -1,4 +1,4 @@
1   -<properties umbraconavihide="0" pagetitle="Service Bus Topics - How To - Node.js - Develop" metakeywords="Service Bus topics Node.js, getting started service bus topics node.js, getting started service bus subscriptions node.j" metadescription="" linkid="dev-nodejs-how-to-service-bus-topics" urldisplayname="Service Bus Topics" headerexpose="" footerexpose="" disquscomments="1"></properties>
  1 +<properties umbraconavihide="0" pagetitle="Service Bus Topics - How To - Node.js - Develop" metakeywords="Service Bus topics Node.js, getting started service bus topics node.js, getting started service bus subscriptions node.j" metadescription="" linkid="dev-nodejs-how-to-service-bus-topics" urldisplayname="Service Bus Topics" headerexpose="" footerexpose="" disquscomments="1"></properties>
2 2
3 3 # How to Use Service Bus Topics/Subscriptions
4 4
@@ -11,7 +11,7 @@ and subscriptions, see the [Next Steps][] section.
11 11
12 12 ## Table of Contents
13 13
14   -- [What are Service Bus Topics and Subscriptions][]
  14 +- [What are Service Bus Topics and Subscriptions?][]
15 15 - [Create a Service Namespace][]
16 16 - [Obtain the Default Management Credentials for the Namespace][]
17 17 - [Create a Node.js Application][]
@@ -24,98 +24,7 @@ and subscriptions, see the [Next Steps][] section.
24 24 - [How to: Delete Topics and Subscriptions][]
25 25 - [Next Steps][1]
26 26
27   -## What are Service Bus Topics and Subscriptions
28   -
29   -Service Bus topics and subscriptions support a **publish/subscribe
30   -messaging communication** model. When using topics and subscriptions,
31   -components of a distributed application do not communicate directly with
32   -each other, they instead exchange messages via a topic, which acts as an
33   -intermediary.
34   -
35   -![Topic Concepts][]
36   -
37   -In contrast to Service Bus queues, where each message is processed by a
38   -single consumer, topics and subscriptions provide a **one-to-many** form
39   -of communication, using a publish/subscribe pattern. It is possible to
40   -register multiple subscriptions to a topic. When a message is sent to a
41   -topic, it is then made available to each subscription to handle/process
42   -independently.
43   -
44   -A topic subscription resembles a virtual queue that receives copies of
45   -the messages that were sent to the topic. You can optionally register
46   -filter rules for a topic on a per-subscription basis, which allows you
47   -to filter/restrict which messages to a topic are received by which topic
48   -subscriptions.
49   -
50   -Service Bus topics and subscriptions enable you to scale to process a
51   -very large number of messages across a very large number of users and
52   -applications.
53   -
54   -## Create a Service Namespace
55   -
56   -To begin using Service Bus topics and subscriptions in Windows Azure,
57   -you must first create a service namespace. A service namespace provides
58   -a scoping container for addressing Service Bus resources within your
59   -application.
60   -
61   -To create a service namespace:
62   -
63   -1. Log on to the [Windows Azure Management Portal][]. In order to perform the following steps you must use the Production portal. If you are currently using the Preview portal, you can switch to Production by clicking **Preview** at the top of the page, and then selecting **Take me to the previous portal**. This will load the production management portal.
64   -
65   - ![preview portal dialog][Previous Management Portal]
66   -
67   -2. In the lower left navigation pane of the Management Portal, click
68   - **Service Bus, Access Control & Caching**.
69   -
70   -3. In the upper left pane of the Management Portal, click the **Service
71   - Bus** node, and then click the **New** button.
72   -
73   - ![image][]
74   -
75   -4. In the **Create a new Service Namespace** dialog, enter a
76   - **Namespace**, and then to make sure that it is unique, click the
77   - **Check Availability** button.
78   -
79   - ![image][2]
80   -
81   -5. After making sure the **Namespace** name is available, choose the
82   - country or region in which your namespace should be hosted (make
83   - sure you use the same **Country/Region** in which you are deploying
84   - your compute resources), and then click the **Create Namespace**
85   - button.
86   -
87   -The namespace you created will then appear in the Management Portal and
88   -takes a moment to activate. Wait until the status is **Active** before
89   -moving on.
90   -
91   -## Obtain the Default Management Credentials for the Namespace
92   -
93   -In order to perform management operations, such as creating a topic or
94   -subscription, on the new namespace, you need to obtain the management
95   -credentials for the namespace.
96   -
97   -1. In the left navigation pane, click the **Service Bus** node to
98   - display the list of available namespaces:
99   -
100   - ![image][]
101   -
102   -2. Select the namespace you just created from the list shown:
103   -
104   - ![image][3]
105   -
106   -3. The right-hand **Properties** pane will list the properties for the
107   - new namespace:
108   -
109   - ![image][4]
110   -
111   -4. The **Default Key** is hidden. Click the **View** button to display
112   - the security credentials:
113   -
114   - ![image][5]
115   -
116   -5. Make a note of the **Default Issuer** and the **Default Key** as you
117   - will use this information below to perform operations with the
118   - namespace.
  27 +<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
119 28
120 29 ## Create a Node.js Application
121 30
@@ -500,9 +409,9 @@ links to learn more.
500 409
501 410 [Azure SDK for Node]: https://github.com/WindowsAzure/azure-sdk-for-node
502 411 [Next Steps]: #nextsteps
503   - [What are Service Bus Topics and Subscriptions]: #What_are_Service_Bus_Topics_and_Subscriptions
504   - [Create a Service Namespace]: #Create_a_Service_Namespace
505   - [Obtain the Default Management Credentials for the Namespace]: #Obtain_the_Default_Management_Credentials_for_the_Namespace
  412 + [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
  413 + [Create a Service Namespace]: #create-a-service-namespace
  414 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
506 415 [Create a Node.js Application]: #Create_a_Nodejs_Application
507 416 [Configure Your Application to Use Service Bus]: #Configure_Your_Application_to_Use_Service_Bus
508 417 [How to: Create a Topic]: #How_to_Create_a_Topic
96 DevCenter/PHP/HowTo/service-bus-queues.md
Source Rendered
@@ -9,9 +9,9 @@ messages**, and **deleting queues**.
9 9
10 10 ## Table of Contents
11 11
12   -- [What are Service Bus queues?](#WhatAreQueues)
13   -- [Create a service namespace](#CreateNamespace)
14   -- [Obtain the default management credentials for the namespace](#GetDefaultCredentials)
  12 +- [What are Service Bus queues?](#what-are-service-bus-queues)
  13 +- [Create a service namespace](#create-a-service-namespace)
  14 +- [Obtain the default management credentials for the namespace](#obtain-default-credentials)
15 15 - [Create a PHP application](#CreateApplication)
16 16 - [Get the Windows Azure Client Libraries](#GetClientLibrary)
17 17 - [Configure your application to use Service Bus](#ConfigureApp)
@@ -21,95 +21,7 @@ messages**, and **deleting queues**.
21 21 - [How to: Handle application crashes and unreadable messages](#HandleCrashes)
22 22 - [Next steps](#NextSteps)
23 23
24   -<h2 id="WhatAreQueues">What are Service Bus queues?</h2>
25   -
26   -Service Bus Queues support a **brokered messaging communication** model.
27   -When using queues, components of a distributed application do not
28   -communicate directly with each other, they instead exchange messages via
29   -a queue, which acts as an intermediary. A message producer (sender)
30   -hands off a message to the queue and then continues its processing.
31   -Asynchronously, a message consumer (receiver) pulls the message from the
32   -queue and processes it. The producer does not have to wait for a reply
33   -from the consumer in order to continue to process and send further
34   -messages. Queues offer **First In, First Out (FIFO)** message delivery
35   -to one or more competing consumers. That is, messages are typically
36   -received and processed by the receivers in the order in which they were
37   -added to the queue, and each message is received and processed by only
38   -one message consumer.
39   -
40   -![Service Bus Queue Diagram][]
41   -
42   -Service Bus queues are a general-purpose technology that can be used for
43   -a wide variety of scenarios:
44   -
45   -- Communication between web and worker roles in a multi-tier Windows
46   - Azure application
47   -- Communication between on-premises apps and Windows Azure hosted apps
48   - in a hybrid solution
49   -- Communication between components of a distributed application
50   - running on-premises in different organizations or departments of an
51   - organization
52   -
53   -Using queues can enable you to scale out your applications better, and
54   -enable more resiliency to your architecture.
55   -
56   -<h2 id="CreateNamespace">Create a service namespace</h2>
57   -
58   -To begin using Service Bus queues in Windows Azure, you must first
59   -create a service namespace. A service namespace provides a scoping
60   -container for addressing Service Bus resources within your application.
61   -
62   -To create a service namespace:
63   -
64   -1. Log on to the [Windows Azure Management Portal][].
65   -2. In the lower left navigation pane of the Management Portal, click
66   - **Service Bus, Access Control & Caching**.
67   -3. In the upper left pane of the Management Portal, click the **Service
68   - Bus** node, and then click the **New** button.
69   -
70   - ![Service Bus Node screenshot][]
71   -
72   -4. In the **Create a new Service Namespace** dialog, enter a
73   - **Namespace**, and then to make sure that it is unique, click the
74   - **Check Availability** button.
75   -
76   - ![Create a New Namespace screenshot][]
77   -
78   -5. After making sure the namespace name is available, choose the
79   - country or region in which your namespace should be hosted (make
80   - sure you use the same country/region in which you are deploying your
81   - compute resources), and then click the **Create Namespace** button.
82   - Having a compute instance is optional, and the service bus can be
83   - consumed from any application with internet access.
84   -
85   - The namespace you created will then appear in the Management Portal
86   - and takes a moment to activate. Wait until the status is **Active**
87   - before moving on.
88   -
89   -<h2 id="GetDefaultCredentials">Obtain the default management credentials for the namespace</h2>
90   -
91   -In order to perform management operations, such as creating a queue, on
92   -the new namespace, you need to obtain the management credentials for the
93   -namespace.
94   -
95   -1. In the left navigation pane, click the **Service Bus** node, to
96   - display the list of available namespaces:
97   -
98   - ![Available Namespaces screenshot][]
99   -
100   -2. Select the namespace you just created from the list shown:
101   -
102   - ![Namespace List screenshot][]
103   -
104   -3. The right-hand **Properties** pane will list the properties for the new namespace:
105   -
106   - ![Properties Pane screenshot][]
107   -
108   -4. The **Default Key** is hidden. Click the **View** button to display the security credentials:
109   -
110   - ![Default Key screenshot][]
111   -
112   -5. Make a note of the **Default Issuer** and the **Default Key** as you will use this information below to perform operations with the namespace.
  24 +<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
113 25
114 26 <h2 id="CreateApplication">Create a PHP application</h2>
115 27
65 DevCenter/PHP/HowTo/service-bus-topics.md
Source Rendered
@@ -7,9 +7,9 @@ subscriptions. The samples are written in PHP and use the [Windows Azure SDK for
7 7
8 8 ## Table of Contents
9 9
10   -- [What are Service Bus Topics and Subscriptions?](#WhatAreTopicsAndSubscriptions)
11   -- [Create a Service Namespace](#CreateNamespace)
12   -- [Obtain the Default Management Credentials for the Namespace](#GetDefaultCredentials)
  10 +- [What are Service Bus Topics and Subscriptions?](#what-are-service-bus-topics)
  11 +- [Create a Service Namespace](#create-a-service-namespace)
  12 +- [Obtain the Default Management Credentials for the Namespace](#obtain-default-credentials)
13 13 - [Create a PHP application](#CreateApplication)
14 14 - [Get the Windows Azure Client Libraries](#GetClientLibrary)
15 15 - [Configure Your Application to Use Service Bus](#ConfigureApp)
@@ -21,64 +21,7 @@ subscriptions. The samples are written in PHP and use the [Windows Azure SDK for
21 21 - [How to: Delete Topics and Subscriptions](#DeleteTopicsAndSubscriptions)
22 22 - [Next Steps](#NextSteps)
23 23
24   -<h2 id="WhatAreTopicsAndSubscriptions">What are Service Bus topics and subscriptions?</h2>
25   -
26   -Service Bus topics and subscriptions support a **publish/subscribe
27   -messaging communication** model. When using topics and subscriptions,
28   -components of a distributed application do not communicate directly with
29   -each other, they instead exchange messages via a topic, which acts as an
30   -intermediary.
31   -
32   -![Service Bus Topics diagram][]
33   -
34   -In contrast to Service Bus queues, where each message is processed by a
35   -single consumer, topics and subscriptions provide a **one-to-many** form
36   -of communication, using a publish/subscribe pattern. It is possible to
37   -register multiple subscriptions to a topic. When a message is sent to a
38   -topic, it is then made available to each subscription to handle/process
39   -independently.
40   -
41   -A topic subscription resembles a virtual queue that receives copies of
42   -the messages that were sent to the topic. You can optionally register
43   -filter rules for a topic on a per-subscription basis, which allows you
44   -to filter/restrict which messages are received by a subscription.
45   -
46   -Service Bus topics and subscriptions enable you to scale to process a
47   -very large number of messages across a very large number of users and
48   -applications.
49   -
50   -<h2 id="CreateNamespace">Create a service namespace</h2>
51   -
52   -To begin using Service Bus queues in Windows Azure, you must first
53   -create a service namespace. A service namespace provides a scoping
54   -container for addressing Service Bus resources within your application.
55   -
56   -To create a service namespace:
57   -
58   -1. Log on to the [Windows Azure Management Portal][].
59   -2. In the lower left navigation pane of the Management Portal, click
60   - **Service Bus, Access Control & Caching**.
61   -3. In the upper left pane of the Management Portal, click the **Service
62   - Bus** node, and then click the **New** button.
63   -
64   - ![Service Bus Node screenshot][]
65   -
66   -4. In the **Create a new Service Namespace** dialog, enter a
67   - **Namespace**, and then to make sure that it is unique, click the
68   - **Check Availability** button.
69   -
70   - ![Create a New Namespace screenshot][]
71   -
72   -5. After making sure the namespace name is available, choose the
73   - country or region in which your namespace should be hosted (make
74   - sure you use the same country/region in which you are deploying your
75   - compute resources), and then click the **Create Namespace** button.
76   - Having a compute instance is optional, and the service bus can be
77   - consumed from any application with internet access.
78   -
79   - The namespace you created will then appear in the Management Portal
80   - and takes a moment to activate. Wait until the status is **Active**
81   - before moving on.
  24 +<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
82 25
83 26 <h2 id="CreateApplication">Create a PHP application</h2>
84 27
102 DevCenter/Python/HowTo/service-bus-queues.md
Source Rendered
@@ -7,7 +7,7 @@ covered include **creating queues, sending and receiving messages**, and
7 7
8 8 ## Table of Contents
9 9
10   -- [What are Service Bus Queues][]
  10 +- [What are Service Bus Queues?][]
11 11 - [Create a Service Namespace][]
12 12 - [Obtain the Default Management Credentials for the Namespace][]
13 13 - [How to: Create a Queue][]
@@ -16,99 +16,7 @@ covered include **creating queues, sending and receiving messages**, and
16 16 - [How to: Handle Application Crashes and Unreadable Messages][]
17 17 - [Next Steps][]
18 18
19   -## <a name="what-queues"> </a>What are Service Bus Queues
20   -
21   -Service Bus Queues support a **brokered messaging communication** model.
22   -When using queues, components of a distributed application do not
23   -communicate directly with each other, they instead exchange messages via
24   -a queue, which acts as an intermediary. A message producer (sender)
25   -hands off a message to the queue and then continues its processing.
26   -Asynchronously, a message consumer (receiver) pulls the message from the
27   -queue and processes it. The producer does not have to wait for a reply
28   -from the consumer in order to continue to process and send further
29   -messages. Queues offer **First In, First Out (FIFO)** message delivery
30   -to one or more competing consumers. That is, messages are typically
31   -received and processed by the receivers in the order in which they were
32   -added to the queue, and each message is received and processed by only
33   -one message consumer.
34   -
35   -![Queue Concepts][]
36   -
37   -Service Bus queues are a general-purpose technology that can be used for
38   -a wide variety of scenarios:
39   -
40   -- Communication between web and worker roles in a multi-tier Windows
41   - Azure application
42   -- Communication between on-premises apps and Windows Azure hosted apps
43   - in a hybrid solution
44   -- Communication between components of a distributed application
45   - running on-premises in different organizations or departments of an
46   - organization
47   -
48   -Using queues can enable you to scale out your applications better, and
49   -enable more resiliency to your architecture.
50   -
51   -## <a name="create-namespace"> </a>Create a Service Namespace
52   -
53   -To begin using Service Bus queues in Windows Azure, you must first
54   -create a service namespace. A service namespace provides a scoping
55   -container for addressing Service Bus resources within your application.
56   -
57   -To create a service namespace:
58   -
59   -1. Log on to the [Windows Azure Management Portal][].
60   -
61   -2. In the lower left navigation pane of the Management Portal, click
62   - **Service Bus, Access Control & Caching**.
63   -
64   -3. In the upper left pane of the Management Portal, click the **Service
65   - Bus** node, and then click the **New** button.
66   -
67   - ![image][]
68   -
69   -4. In the **Create a new Service Namespace** dialog, enter a
70   - **Namespace**, and then to make sure that it is unique, click the
71   - **Check Availability** button.
72   -
73   - ![image][1]
74   -
75   -5. After making sure the namespace name is available, choose the
76   - country or region in which your namespace should be hosted (make
77   - sure you use the same country/region in which you are deploying your
78   - compute resources), and then click the **Create Namespace** button.
79   -
80   -The namespace you created will then appear in the Management Portal and
81   -takes a moment to activate. Wait until the status is **Active** before
82   -moving on.
83   -
84   -## <a name="obtain-creds"> </a>Obtain the Default Management Credentials for the Namespace
85   -
86   -In order to perform management operations, such as creating a queue, on
87   -the new namespace, you need to obtain the management credentials for the
88   -namespace.
89   -
90   -1. In the left navigation pane, click the **Service Bus** node, to
91   - display the list of available namespaces:
92   -
93   - ![image][]
94   -
95   -2. Select the namespace you just created from the list shown:
96   -
97   - ![image][2]
98   -
99   -3. The right-hand **Properties** pane will list the properties for the
100   - new namespace:
101   -
102   - ![image][3]
103   -
104   -4. The **Default Key** is hidden. Click the **View** button to display
105   - the security credentials:
106   -
107   - ![image][4]
108   -
109   -5. Make a note of the **Default Key** as you will use this information
110   - below to perform operations with the namespace.
111   -
  19 +<div chunk="../../shared/chunks/howto-service-bus-queues.md" />
112 20
113 21 **Note:** If you need to install Python or the Client Libraries, please see the [Python Installation Guide](../commontasks/how-to-install-python.md).
114 22
@@ -228,9 +136,9 @@ links to learn more.
228 136 - See the MSDN Reference: [Queues, Topics, and Subscriptions.][]
229 137
230 138 [Next Steps]: #next-steps
231   - [What are Service Bus Queues]: #what-queues
232   - [Create a Service Namespace]: #create-namespace
233   - [Obtain the Default Management Credentials for the Namespace]: #obtain-creds
  139 + [What are Service Bus Queues?]: #what-are-service-bus-queues
  140 + [Create a Service Namespace]: #create-a-service-namespace
  141 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
234 142 [How to: Create a Queue]: #create-queue
235 143 [How to: Send Messages to a Queue]: #send-messages
236 144 [How to: Receive Messages from a Queue]: #receive-messages
99 DevCenter/Python/HowTo/service-bus-topics.md
Source Rendered
@@ -9,7 +9,7 @@ and subscriptions, see the [Next Steps][] section.
9 9
10 10 ## Table of Contents
11 11
12   -- [What are Service Bus Topics and Subscriptions][]
  12 +- [What are Service Bus Topics and Subscriptions?][]
13 13 - [Create a Service Namespace][]
14 14 - [Obtain the Default Management Credentials for the Namespace][]
15 15 - [How to: Create a Topic][]
@@ -20,96 +20,7 @@ and subscriptions, see the [Next Steps][] section.
20 20 - [How to: Delete Topics and Subscriptions][]
21 21 - [Next Steps][1]
22 22
23   -## What are Service Bus Topics and Subscriptions
24   -
25   -Service Bus topics and subscriptions support a **publish/subscribe
26   -messaging communication** model. When using topics and subscriptions,
27   -components of a distributed application do not communicate directly with
28   -each other, they instead exchange messages via a topic, which acts as an
29   -intermediary.
30   -
31   -![Topic Concepts][]
32   -
33   -In contrast to Service Bus queues, where each message is processed by a
34   -single consumer, topics and subscriptions provide a **one-to-many** form
35   -of communication, using a publish/subscribe pattern. It is possible to
36   -register multiple subscriptions to a topic. When a message is sent to a
37   -topic, it is then made available to each subscription to handle/process
38   -independently.
39   -
40   -A topic subscription resembles a virtual queue that receives copies of
41   -the messages that were sent to the topic. You can optionally register
42   -filter rules for a topic on a per-subscription basis, which allows you
43   -to filter/restrict which messages to a topic are received by which topic
44   -subscriptions.
45   -
46   -Service Bus topics and subscriptions enable you to scale to process a
47   -very large number of messages across a very large number of users and
48   -applications.
49   -
50   -## Create a Service Namespace
51   -
52   -To begin using Service Bus topics and subscriptions in Windows Azure,
53   -you must first create a service namespace. A service namespace provides
54   -a scoping container for addressing Service Bus resources within your
55   -application.
56   -
57   -To create a service namespace:
58   -
59   -1. Log on to the [Windows Azure Management Portal][].
60   -
61   -2. In the lower left navigation pane of the Management Portal, click
62   - **Service Bus, Access Control & Caching**.
63   -
64   -3. In the upper left pane of the Management Portal, click the **Service
65   - Bus** node, and then click the **New** button.
66   -
67   - ![image][]
68   -
69   -4. In the **Create a new Service Namespace** dialog, enter a
70   - **Namespace**, and then to make sure that it is unique, click the
71   - **Check Availability** button.
72   -
73   - ![image][2]
74   -
75   -5. After making sure the **Namespace** name is available, choose the
76   - country or region in which your namespace should be hosted (make
77   - sure you use the same **Country/Region** in which you are deploying
78   - your compute resources), and then click the **Create Namespace**
79   - button.
80   -
81   -The namespace you created will then appear in the Management Portal and
82   -takes a moment to activate. Wait until the status is **Active** before
83   -moving on.
84   -
85   -## Obtain the Default Management Credentials for the Namespace
86   -
87   -In order to perform management operations, such as creating a topic or
88   -subscription, on the new namespace, you need to obtain the management
89   -credentials for the namespace.
90   -
91   -1. In the left navigation pane, click the **Service Bus** node to
92   - display the list of available namespaces:
93   -
94   - ![image][]
95   -
96   -2. Select the namespace you just created from the list shown:
97   -
98   - ![image][3]
99   -
100   -3. The right-hand **Properties** pane will list the properties for the
101   - new namespace:
102   -
103   - ![image][4]
104   -
105   -4. The **Default Key** is hidden. Click the **View** button to display
106   - the security credentials:
107   -
108   - ![image][5]
109   -
110   -5. Make a note of the **Default Issuer** and the **Default Key** as you
111   - will use this information below to perform operations with the
112   - namespace.
  23 +<div chunk="../../shared/chunks/howto-service-bus-topics.md" />
113 24
114 25 **Note:** If you need to install Python or the Client Libraries, please see the [Python Installation Guide](../commontasks/how-to-install-python.md).
115 26
@@ -323,9 +234,9 @@ links to learn more.
323 234 - API reference for [SqlFilter][].
324 235
325 236 [Next Steps]: #nextsteps
326   - [What are Service Bus Topics and Subscriptions]: #What_are_Service_Bus_Topics_and_Subscriptions
327   - [Create a Service Namespace]: #Create_a_Service_Namespace
328   - [Obtain the Default Management Credentials for the Namespace]: #Obtain_the_Default_Management_Credentials_for_the_Namespace
  237 + [What are Service Bus Topics and Subscriptions?]: #what-are-service-bus-topics
  238 + [Create a Service Namespace]: #create-a-service-namespace
  239 + [Obtain the Default Management Credentials for the Namespace]: #obtain-default-credentials
329 240 [How to: Create a Topic]: #How_to_Create_a_Topic
330 241 [How to: Create Subscriptions]: #How_to_Create_Subscriptions
331 242 [How to: Send Messages to a Topic]: #How_to_Send_Messages_to_a_Topic
71 DevCenter/Shared/Chunks/howto-service-bus-queues.md
Source Rendered
... ... @@ -1,4 +1,5 @@
1   -## <a name="what-queues"> </a>What are Service Bus Queues
  1 +<a id="what-are-service-bus-queues"></a>
  2 +<h2>What are Service Bus Queues?</h2>
2 3
3 4 <span>Service Bus Queues support a **brokered messaging communication**
4 5 model. When using queues, components of a distributed application do not
@@ -30,4 +31,70 @@ a wide variety of scenarios:
30 31 Using queues can enable you to scale out your applications better, and
31 32 enable more resiliency to your architecture.
32 33
33   - [Queue Concepts]: ../../../DevCenter/dotNet/Media/sb-queues-08.png
  34 +<a id="create-a-service-namespace"></a>
  35 +<h2>Create a Service Namespace</h2>
  36 +
  37 +To begin using Service Bus queues in Windows Azure, you must first
  38 +create a service namespace. A service namespace provides a scoping
  39 +container for addressing Service Bus resources within your application.
  40 +
  41 +To create a service namespace:
  42 +
  43 +1. Log on to the [Windows Azure Management Portal][].
  44 +
  45 +2. In the left navigation pane of the Management Portal, click
  46 + **Service Bus**.
  47 +
  48 +3. In the lower pane of the Management Portal, click **Create**.
  49 + ![][0]
  50 +
  51 +4. In the **Add a new namespace** dialog, enter a namespace name.
  52 + The system immediately checks to see if the name is available.
  53 + ![][1]
  54 +
  55 +5. After making sure the namespace name is available, choose the
  56 + country or region in which your namespace should be hosted (make
  57 + sure you use the same country/region in which you are deploying your
  58 + compute resources).
  59 +
  60 + IMPORTANT: Pick the **same region** that you intend to choose for
  61 + deploying your application. This will give you the best performance.
  62 +
  63 +6. Click the check mark. The system now creates your service
  64 + namespace and enables it. You might have to wait several minutes as
  65 + the system provisions resources for your account.
  66 +
  67 + ![][5]
  68 +
  69 +The namespace you created will then appear in the Management Portal and
  70 +takes a moment to activate. Wait until the status is **Active** before
  71 +continuing.
  72 +
  73 +<a id="obtain-default-credentials"></a>
  74 +<h2>Obtain the Default Management Credentials for the Namespace</h2>
  75 +
  76 +In order to perform management operations, such as creating a queue, on
  77 +the new namespace, you must obtain the management credentials for the
  78 +namespace.
  79 +
  80 +1. In the left navigation pane, click the **Service Bus** node, to
  81 + display the list of available namespaces:
  82 + ![][6]
  83 +
  84 +2. Select the namespace you just created from the list shown:
  85 + ![][2]
  86 +
  87 +3. Click **Access Key**.
  88 + ![][3]
  89 +
  90 +4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
  91 +
  92 + [Windows Azure Management Portal]: http://manage.windowsazure.com
  93 + [Queue Concepts]: ../../../DevCenter/dotNet/Media/sb-queues-08.png
  94 + [Windows Azure Management Portal]: http://manage.windowsazure.com
  95 + [0]: ../../../DevCenter/dotNet/Media/sb-queues-03.png
  96 + [1]: ../../../DevCenter/dotNet/Media/sb-queues-04.png
  97 + [2]: ../../../DevCenter/dotNet/Media/sb-queues-09.png
  98 + [3]: ../../../DevCenter/dotNet/Media/sb-queues-06.png
  99 + [5]: ../../../DevCenter/dotNet/Media/getting-started-multi-tier-27.png
  100 + [6]: ../../../DevCenter/dotNet/Media/sb-queues-13.png
67 DevCenter/Shared/Chunks/howto-service-bus-topics.md
Source Rendered
... ... @@ -1,4 +1,5 @@
1   -## <a name="what-is"> </a>What are Service Bus Topics and Subscriptions
  1 +<a id="what-are-service-bus-topics"></a>
  2 +<h2>What are Service Bus Topics and Subscriptions</h2>
2 3
3 4 Service Bus topics and subscriptions support a **publish/subscribe
4 5 messaging communication** model. When using topics and subscriptions,
@@ -25,4 +26,66 @@ Service Bus topics and subscriptions enable you to scale to process a
25 26 very large number of messages across a very large number of users and
26 27 applications.
27 28
28   - [Topic Concepts]: ../../../DevCenter/dotNet/Media/sb-topics-01.png
  29 +<a id="create-a-service-namespace"></a>
  30 +<h2>Create a Service Namespace</h2>
  31 +
  32 +To begin using Service Bus topics and subscriptions in Windows Azure,
  33 +you must first create a service namespace. A service namespace provides
  34 +a scoping container for addressing Service Bus resources within your
  35 +application.
  36 +
  37 +To create a service namespace:
  38 +
  39 +1. Log on to the [Windows Azure Management Portal][].
  40 +
  41 +2. In the left navigation pane of the Management Portal, click
  42 + **Service Bus**.
  43 +
  44 +3. In the lower pane of the Management Portal, click **Create**.
  45 + ![][0]
  46 +
  47 +4. In the **Add a new namespace** dialog, enter a namespace name.
  48 + The system immediately checks to see if the name is available.
  49 + ![][2]
  50 +
  51 +5. After making sure the namespace name is available, choose the
  52 + country or region in which your namespace should be hosted (make
  53 + sure you use the same country/region in which you are deploying your
  54 + compute resources).
  55 +
  56 + IMPORTANT: Pick the **same region** that you intend to choose for
  57 + deploying your application. This will give you the best performance.
  58 +
  59 +6. Click the check mark. The system now creates your service
  60 + namespace and enables it. You might have to wait several minutes as
  61 + the system provisions resources for your account.
  62 +
  63 + ![][6]
  64 +
  65 +<a id="obtain-default-credentials"></a>
  66 +<h2>Obtain the Default Management Credentials for the Namespace</h2>
  67 +
  68 +In order to perform management operations, such as creating a topic or
  69 +subscription, on the new namespace, you need to obtain the management
  70 +credentials for the namespace.
  71 +
  72 +1. In the left navigation pane, click the **Service Bus** node to
  73 + display the list of available namespaces:
  74 + ![][0]
  75 +
  76 +2. Select the namespace you just created from the list shown:
  77 + ![][3]
  78 +
  79 +3. Click **Access Key**.
  80 + ![][4]
  81 +
  82 +4. In the **Connect to your namespace** dialog, find the **Default Issuer** and **Default Key** entries. Make a note of these values, as you will use this information below to perform operations with the namespace.
  83 +
  84 + [Topic Concepts]: ../../../DevCenter/dotNet/Media/sb-topics-01.png
  85 + [Windows Azure Management Portal]: http://manage.windowsazure.com
  86 + [0]: ../../../DevCenter/dotNet/Media/sb-queues-13.png
  87 + [2]: ../../../DevCenter/dotNet/Media/sb-queues-04.png
  88 + [3]: ../../../DevCenter/dotNet/Media/sb-queues-09.png
  89 + [4]: ../../../DevCenter/dotNet/Media/sb-queues-06.png
  90 + [5]: ../../../DevCenter/dotNet/Media/sb-queues-07.png
  91 + [6]: ../../../DevCenter/dotNet/Media/getting-started-multi-tier-27.png
88 DevCenter/dotNET/HowTo/service-bus-queues.md
Source Rendered
@@ -9,93 +9,7 @@ samples are written in C\# and use the .NET API. The scenarios covered
9 9 include **creating queues, sending and receiving messages**, and
10 10 **deleting queues**. For more information on queues, see the [Next Steps] section. </span>
11 11
12   -<h2><span class="short-header">What are Service Bus Queues</span>What are Service Bus Queues</h2>
13   -
14   -<span>Service Bus Queues support a **brokered messaging communication**
15   -model. When using queues, components of a distributed application do not
16   -communicate directly with each other, they instead exchange messages via
17   -a queue, which acts as an intermediary. A message producer (sender)
18   -hands off a message to the queue and then continues its processing.
19   -Asynchronously, a message consumer (receiver) pulls the message from the
20   -queue and processes it. The producer does not have to wait for a reply
21   -from the consumer in order to continue to process and send further
22   -messages. Queues offer **First In, First Out (FIFO)** message delivery
23   -to one or more competing consumers. That is, messages are typically
24   -received and processed by the receivers in the order in which they were
25   -added to the queue, and each message is received and processed by only
26   -one message consumer.</span>
27   -
28   -![Queue Concepts][]
29   -
30   -Service Bus queues are a general-purpose technology that can be used for
31   -a wide variety of scenarios:
32   -
33   -- Communication between web and worker roles in a multi-tier Windows
34   - Azure application
35   -- Communication between on-premises apps and Windows Azure hosted apps
36   - in a hybrid solution
37   -- Communication between components of a distributed application
38   - running on-premises in different organizations or departments of an
39   - organization
40