12/10/2023 0 Comments Azure storage queue fifo![]() ![]() Your architecture needs to allow room for a Windows Service. When then should one use Azure Service Bus and when to use an Azure Storage Queue? Differencesįrom an architecture perspective, a Storage Queue receive is usually a Windows service that loops to check if the queue has a new message ready to be processed. ![]() In other words, if you want your messages to be processed as soon as possible, you have the option of spinning up many instances of your receivers so that messages can be retrieved and deleted as soon as it is picked up from the queue. These two services can also have multiple receivers hence load balancing the messages. In our example, the receiver can notify the shipping application that an order is ready to be shipped or email recipient the status of their order. The Service Bus or Storage Queue has one or more receivers that’s ready to process messages from the queue. ![]() The sender can be web application that would like to notify other apps that, for instance, an order has been submitted or a message was posted ready to be processed. Service Bus (queue/topic) and Storage queue are both queue system that stores messages to be retrieved by a client or receiver. Microsoft Documentation outlines some of the technical differences such as message size, push-style, but I wanted to share my experience deciding between Azure Service Bus and Storage Queue. Service Bus queues and topics can be confused with Azure Storage Queue, even though they each solve a specific problem. With many Azure services available, it may be sometimes hard to know what is the right service for the specific problem you are trying to solve. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |