AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Azure storage queue fifo9/27/2023 ![]() This functionality allows us to decouple components within our architecutre, since producers and consumers don’t need to be concerned with what the other one is doing. Producers can keep sending messages to the queue. The message will be stored in the queue and will only be processed once the consumer pulls the message off the queue. One of the benefits of using queues is that the producers and consumer of the queue don’t have to send and receive the message at the same time. To process the message, the client will pull the message off the queue. ![]() The queue will store this message until our client is able to process them. ![]() This means that clients that receive messages from the queue and then process that message in the order in which they were added to the queue, and they will be the only consumer that processes this message. Queues work on a First In, First Out (FIFO) basis. Feel free to deploy the infrastructure code to your own Azure subscription, or code the Service Bus resources yourself using my Bicep templates as a guide: Sample I’ve created a couple of samples that you can refer to as you read through this post. In the article, I’ll explain what the differences are between queues and topics in Azure Service Bus, how we can provision Service Bus namespaces with either queues or topics using Bicep and then I’ll show you how we can send and receives messages from our queue or topic. Azure Service Bus is a message broker that we can use to send messages to queues or publish messages to topics so that consumers can subscribe to those topics to receive those messages.
0 Comments
Read More
Leave a Reply. |