This course introduces the Azure Service Bus.
- Gain a basic understanding of what Azure Service Bus is, what it does, and how it can be managed
- Those who wish to learn about Azure Service Bus
- Basic familiarity with Azure
- Basic familiarity with distributed apps
Welcome to Facilitating Efficient Messaging with Azure Service Bus. Azure Service Bus uses various message properties to facilitate efficient messaging and to manage messaging entities effectively.
The MessageId property is a unique identifier for each message and can be used to track messages and ensure that they are not duplicated. The CorrelationId property is used to correlate related messages and can be used to group messages that belong to a particular transaction or activity.
The SessionID property is used to group related messages together and to enable first-in, first-out (FIFO) ordering of messages within a session. The ReplyToSessionId property is used to enable request-response messaging patterns within a session by indicating which session should receive the response message. In summary, these message properties play important roles in enabling efficient messaging and managing messaging entities effectively in Azure Service Bus.
In Azure Service Bus, filter types are used to allow users to filter messages based on certain conditions or criteria. The platform supports three types of filters: SQL filters, Boolean filters, and Correlation filters.
A SQL filter is used to hold a SQL-like conditional expression that is evaluated in the broker against the arriving messages user-defined properties and system properties. Boolean filters allow users to match messages based on true or false conditions, while Correlation filters enable users to filter messages based on correlation IDs, message types, and other custom properties.
Filters can be used to subscribe to specific messages, to route messages to different queues, or to perform various other actions. They are an essential feature in Service Bus, enabling users to better manage their message flows and tailor their message processing to meet specific business needs.
Speaking of message sessions, Azure Service Bus supports first in, first out (FIFO) messaging using those message sessions that I mentioned.
Because sessions allow related messages to be handled in order and jointly, they enable FIFO and request-response patterns. In other words, when a sender creates a message with a session ID, all messages with the same session ID are guaranteed to be processed in the order they were sent. This ensures that the first message sent with a particular session ID is the first message received and processed by the receiver.
I should mention that the Basic tier of Azure Service Bus does not support sessions, but they ARE available in the Standard and Premium tiers, which we’ll touch on in the next lesson.
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.