- Azure for Architects
- Ritesh Modi
- 175字
- 2021-07-08 09:33:38
Priority queue
There is often a need when messages with higher importance should be given priority in processing compared to general messages with lower priority. This pattern is important for applications that provide different service level agreements (SLA) to consumers, which provide services based on different plans and subscriptions.
Queues follow first-in, first-out patterns. Messages are processed in sequence. However, with the help of this pattern, it is possible to fast-track processing of certain messages due to their higher priority. There are multiple ways to implement it. If the queue provides the capability of assigning priority and based on priority re-order messages, then even a single queue is enough to implement this pattern.
However, if the queue does not have the capability to re-order messages, then separate queues can be created for different priorities and each queue can have separate consumers associated with it.

In fact, this pattern can reuse competing consumer patterns if needed to fast-track processing of messages from each queue using multiple consumers.
- DevOps:軟件架構師行動指南
- Java應用與實戰
- Building Modern Web Applications Using Angular
- C語言程序設計案例教程(第2版)
- C#編程入門指南(上下冊)
- Twilio Best Practices
- Learning Network Forensics
- Python忍者秘籍
- 領域驅動設計:軟件核心復雜性應對之道(修訂版)
- R用戶Python學習指南:數據科學方法
- Visual Basic 6.0程序設計實驗教程
- 代替VBA!用Python輕松實現Excel編程
- 物聯網系統架構設計與邊緣計算(原書第2版)
- Java Hibernate Cookbook
- RESTful Web API Design with Node.js(Second Edition)