Through this section of the Azure tutorial you will learn what is the Azure Service Bus, its concept and fundamentals, queues and relays in Azure Service Bus and more.
3.1 K Views
What is Azure Service Bus?
Microsoft Azure Service Bus is a reliable information delivery service.
The main agenda is to make the communication easier.
When two or more parties want to exchange information, they need a communication facilitator.
Service Bus is a brokered, or third-party communication mechanism.
Watch this Azure Certification AZ-203 video
Azure Service Bus: Concept
Azure service bus is a multi- tenant cloud service. multiple users share the services. The application developer who creates a namespace, then defines the communication mechanisms needed within that namespace.
Azure Service Bus Fundamentals
Queues allows one way communication.
Each queue acts a broker that stores sent messages until they are
A single recipient receives every single message.
The Topics help in one-way communication
The Topic is similar to a broker, but they also help you to filter the received message to match the specific criteria
Relays provide bi-directional communication.
When compared to queues and topics relays don’t act like a broker.
Instead, it just passes them on to the destination application.
Azure Service Bus: Queues
When the user decides to connect two application is using a Service Bus queue. The process is carried out when the sender sends a message to a Service Bus Queue and a receiver picks up the message at some point of time. It is to be noted that a queue can have just a single receiver.
Every individual message has two parts
A set of properties each of which is a key and a message payload.
A receiver can read the message from a Service Bus queue in two different ways
Receive & delete: Receives a message from the queue and deletes it immediately
Peek Lock : It removes the message from the queue, it does not delete the message instead it locks the message making it invisible to other
Azure Service Bus: Relay
A one- way asynchronous communication is provided by both queues and topics through a broker.
Ina relay there the traffic flows in just one direction and there is no direct connection between senders and receivers.
You don’t need a broker to store a message when your application needs to both send and receive messages