A brief article today to have a quick run through of what Azure Service Bus is and why would you want to use it in your application.

Microsoft Azure Service Bus is fundamentally a fully managed integration message broker. This service can aid in the configuration and creation of loosely coupled applications and services.

This service offers a secure and reliable platform for asynchronous transfer of data and state. Messages can be sent on Azure Service Bus that contain data destined to be consumed by other services and/or applications. Messages are sent in a binary format i.e. JSON, XML or plain text.

Common Messaging scenarios:

• Messaging – The transfer of business data.
• Decouple applications – To improve the reliability and scalability of apps and services (i.e. clients don’t have to all be online at the same time of messages being sent/received)
• Topics and subscriptions – A common enablement of 1:n relationships in a publisher/subscriber configuration.
• Message sessions – To implement workflows that require message ordering or message deferral.

Azure service Bus is made up of 3 key component concepts:

Namespaces

The concept of a namespace can be viewed as a container for all messaging components. Multiple queues and topics can all be stored in a single namespace with namespaces often serving as an application container.

Queues

Messages are sent to and received from queues. Queues store messages until the receiving application is available to receive and process them.

Topics

Topics can also be used to send and receive messages. Whilst queues are often used for point to point communications, Topics are useful in a publish/subscribe scenario offering the one to many concept of asynchronous messaging.

Topics can have multiple, independent subscriptions. A subscriber to a topic can receive a copy of each message sent to that topic. Subscriptions are named entities. Subscriptions persist, but can expire or autodelete.

Azure Service Bus also has a number of advanced features

• Message sessions
• Autoforwarding
• Dead-letter queue
• Scheduled delivery
• Message deferral
• Batching
• Transactions
• Filtering and actions
• Autodelete on idle
• Duplicate detection
• Security Protocols Supported by Service Bus: SAS, RBAC, Managed Identities
• Geo-disaster recovery
• Security: AMQP 1.0, HTTP/REST
• Client Libraries Supported by Service Bus: .NET, Java, JMS

100DaysOfCloud Overview

My Main ReadMe Page is all set up with a bit about me!

The guys at 100DaysofCloud have set up the GitHub repo to be cloned and also have a great repo containing ideas and areas to collaborate on: https://github.com/100DaysOfCloud/100DaysOfCloudIdeas

My Github Journey tracker can be found here: https://github.com/jonnychipz/100DaysOfCloud

Please Watch/Star my repo and feel free to comment of contribute to anything I push! I really look forward to hearing from anyone who is going to jump on the journey around the same time as me! Lets see where I get to in 100 days!

I would encourage others to jump on this journey, I’m not sure that I will be able to commit every day for 100 days, but as long as I can complete 100 days that will be great!