If you have multiple destinations for a single message, but need queue-like behavior, use topics. That is, receivers typically receive and process messages in the order in which they were added to the queue. Queues offer First In, First Out (FIFO) message delivery to one or more competing consumers. For more advanced needs, use Service Bus queues. Azure Service Bus supports reliable message queuing and durable publish/subscribe messaging. Use Storage queues when you want a simple and easy-to-code queue system. Use a queue to organize messages and gracefully handle unpredictable surges in demand. You want to track progress for processing a message inside of the queue.Ī queue is a simple, temporary storage location for messages sent between the components of a distributed application. You expect the queue to exceed 80 GB in size. You need an audit trail of all messages that pass through the queue. In addition, it’s the best solution if your app has any of the following requirements. Queue storage isn’t quite as feature-rich, but if you don’t need any of those features, it can be a simpler choice. You would like to be able to publish and consume batches of messages. Your queue size will not grow larger than 80 GB. You need to handle messages larger than 64 KB but less than 256 KB. You need to provide a role-based access model to the queues. You want to receive messages without polling the queue. You need to group messages into transactions. You need an At-Most-Once delivery guarantee. You need multiple receivers to handle each message Choose Service Bus queues if Each has a slightly different feature set, which means you can choose one or the other, or use both, depending on the problem you are solving.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |