What's new in Azure Service Bus

1. What's new in Azure Service Bus Abhishek Lal @AbhishekRLal Senior Program Manager Windows Azure

2. Service Bus releases SDK 2.1 – 7/13 • AMQP • Paired Namespaces SDK 2.0 – 4/13 • Shared Access Secrets (SAS) • Auto-delete Idle Entities • Event-Driven Model • Task-based Async APIs • Browsing Messages SDK 1.8 – 10/12 • Message Lock Renewal • Entity Query • Forward Messages between entities • Batch APIs • Browse Sessions • Updating Entities (enable\disable) SDK 2.1 preview SB1.1 Preview – 6/13 • Consistent features with Azure SDK 2.1 • Interoperability with AMQP 1.0 • Shared Access Signature (SAS) auth model • Admin & Tenant Management Portal SB1.0 – 10/12 • Brokered Messaging: Queues and Topics • Consistent & Supported with SDK1.8

3. What’s new in Service Bus Service Bus 1.1 for Windows Server – 10/18 Symmetric features in Server and Service with Azure SDK 2.1 Part of Windows Azure Pack AMQP 1.0 support Azure SDK 2.2 – 10/22 Visual Studio 2013 support Partitioned Queues & Topics AMQP client support for SAS auth

4. Service Bus 1.1 for Windows Server Part of Windows Azure Pack release Consistent features with Azure SDK 2.1 Interoperability with AMQP 1.0 Shared Access Signature (SAS) auth model Admin & Tenant Management Portal

5. Windows Azure Pack Self Service Portal Moves On-Premises Windows Azure Private Service Provider Subscriber Self-ServicePortal Web Sites Web Sites Web Sites Service Web Sites Apps Apps Databases Plans Apps Service Admin VMs Self-ServicePortal VMs Self-ServicePortal Subscriber Self-ServicePortal VMs Users Database VMs Common Mgt. Experience Service Management API Service Management API Service Bus Others VM Role Worker Role Web Sites Web Sites Caching SQL Service Bus Other Services CDN. Media,, etc. Shared Cloud Services Messaging, Caching Hadoop, etc. Cloud-Enabled Services Move On-Premises SP1 w/ Service Provider Foundation Workload Portability Consistent Dev. Experience

6. Service Bus Deployment – Standalone

7. Service Bus Deployment – Windows Azure Pack Administrators Experience Tenant Experience

8. Advanced Message Queuing Protocol 1.0 • Open, standard messaging protocol • Enables cross-platform apps to be built using brokers, libraries and frameworks from different vendors • Features • Efficient – binary connection-oriented protocol • Reliable – fire-and-forget to reliable, exactly-once delivery • Portable data representation – cross-platform, full-fidelity exchange • Flexible – client-client, client-broker, and broker-broker topologies • Broker-model independent – no requirements on broker internals AMQP

9. AMQP 1.0 Standardization • OASIS announced the ratification of the AMQP 1.0 Standard in October 2012 • The culmination of several years effort by more than 20 companies • Technology vendors: Axway Software, Huawei Technologies, IIT Software, INETCO Systems, Kaazing, Microsoft, Mitre Corporation, Primeton Technologies, Progress Software, Red Hat, SITA, Software AG, Solace Systems, VMware, WSO2, Zenika. User firms: Bank of America, Credit Suisse, Deutsche Boerse, Goldman Sachs, JPMorgan Chase • Service Bus supports AMQP 1.0!

10. Programming Model Options Apps Windows Whatever Java/JMS Apache Qpid JMS AMQP 1.0 C/C++(incl Embedded) Apache Proton-C Node.js client .NET WCF Service Model .NET Service Bus Messaging API Any HTTPclient Pythonclient PHPclient NetMessagingBinding AMQP 1.0 HTTP(S) SB Messaging Protocol(net.tcp, proprietary) Service Bus

11. Messaging SDK / Libraries Apps/Services on Windows Service Bus Queues & Topics Apps/Services on other platforms AMQP 1.0 SBMP(net.tcp, proprietary) AMQP 1.0 https://github.com/windowsAzure/ HTTP(S) /azure-sdk-for-java/ /azure-sdk-for-node/ /azure-sdk-for-php/ Samples / Prototypes /azure-sdk-for-ruby/ HTTP(S) /azure-sdk-for-python/

12. AMQP 1.0 with Proton-C libraryand Visual Studio 2013 support Demo

13. Azure SDK 2.2 – 10/22 • Visual Studio 2013 support • Partitioned Queues and Topics

14. Partitioned Queues and Topics Partitioned entities spread messages across several nodes Allow for 16GB to 80GB Queues/Topics Resilient to unavailability of storage units Need higher throughput Larger Queues and Topics Increase the availability of entities // Create partitioned topic NamespaceManagernm = NamespaceManager.CreateFromConnectionSTring(myConnectionString); TopicDescriptiontd = newTopicDescription(myTopicName); td.EnablePartitioning = true; nm.CreateTopic(td);

15. Partitioned entities – advanced concepts • Sessions • Achieve correlation of related messages by setting SessionId • All messages for same SessionId are co-located and support ordering • Full support to SetState/GetState and other Session semantics • PartitionKey • By default we assign a Partition to any incoming message • Use this property if you are not using sessions and need transactions • Allows you to send messages for same transaction scope to same partition • MessageId • Primarily used of duplicate detection when set by the user • Deduplication fully supported for Partitioned entities based on MessageId

16. Service Bus Overview Documentation Subscribe! Tutorials Azure SDK – New Features Download What’s new (Service Bus) Partitioned Queues & Topics All Service Bus Samples AMQP 1.0 support Overview Developer Guide .NET Tutorial Java Tutorial Service Bus 1.1 for Windows Server Windows Azure pack Azure pack blog post Overview Release Notes Getting Started Resources