1. Bill Chesnut Microsoft BizTalk Virtual Technical Specialist BizTalk Server MVP Principal Consultant for Mexia Bill@mexia.com.au

2. Windows Azure Service Bus Reliable,. Messaging Queuing Pub/Sub Reliable Transfer Messaging Queuing Pub/Sub Reliable Transfer Connectivity Service Relay Protocol Tunnel Eventing, Push Connectivity Service Relay Protocol Tunnel Eventing, Push

3. Windows Azure Service Bus Reliable, Messaging Queuing Pub/Sub Reliable Transfer Messaging Queuing Pub/Sub Reliable Transfer. Connectivity Service Relay Protocol Tunnel Eventing, Push Connectivity Service Relay Protocol Tunnel Eventing, Push

4. Service Bus Relay Service Bus Sender Receiver Frontend Nodes Ctrl Forwarder outboun d socket connect outbound socket rendezvous Ctrl NLB Integrated w/ WCF programming model Using Outbound Connections Only No open inbound firewall/NAT ports Outbound connections default to TCP Fall back to HTTP when needed Guarded by Datacenter Firewall Secured with Access Control

5. Demo

6. Windows Azure Service Bus Reliable,. Messaging Queuing Pub/Sub Reliable Transfer Messaging Queuing Pub/Sub Reliable Transfer Connectivity Service Relay Protocol Tunnel Eventing, Push Connectivity Service Relay Protocol Tunnel Eventing, Push

7. Messages Brokered messaging properties are not SOAP headers Properties are key/value pairs that may very well carry payloads Its not uncommon to have messages with empty message bodies Message bodies are useful for a single opaque payload not exposed to the broker (e.g. encrypted content) Broker Message Body Properties

8. Patterns

9. Brokered Transfer Load Leveling Receiver receives and processes at its own pace. Can never be overloaded. Can add receivers as queue length grows, reduce receiver if queue length is low or zero. Gracefully handles traffic spikes by never stressing out the backend. Offline/Batch Allows taking the receiver offline for servicing or other reasons. Requests are buffered up until the receiver is available again. Queue

10. Competing Consumer Load Balancing Multiple receivers compete for messages on the same queue (or subscription). Provides automatic load balancing of work to receivers volunteering for jobs. Observing the queue length allows to determine whether more receivers are required. Queue

11. Fan-In Concentrator Fan information into a single queue from a range of data sources Multi-Stage Aggregation / Rollup Fan into a set of queues, perform aggregation/roll-up/reduction and fan further. Queue

12. Taps and Fan-Out Message Distribution Each receiver gets its own copy of each message. Subscriptions are independent. Allows for many independent taps into a message stream. Subscriber can filter down by interest. Constrained Message Distribution (Partitioning) Receiver get mutually exclusive slices of the message stream by creating appropriate filter expressions. Topic Sub

13. Filtering Up to 2000 rules per subscription Each matched rule yields a message copy SQL92 expressions over message properties Topic Sub

14. Partitioning Rule conditions form mutually exclusive ranges Allows partitioning-aware message distribution No need for sender to be aware of partitioning Topic Sub

15. Demo

16. Questions

17. References http://channel9.msdn.com/Events/BUILD/BUILD2011/SAC-862T http://channel9.msdn.com/posts/ServiceBusTopicsAndQueues http://blogs.msdn.com/b/windowsazure/