Broker-Based Pub-Sub Performance Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing pub-sub architectures lack provisions for handling time-critical traffic, relying on best-effort delivery and limited quality of service guarantees, which can lead to inefficiencies and poor performance in distributed systems.
Innovation Solution
A method for managing performance in a distributed system with a broker-based publish-subscribe architecture, which involves determining performance requirements, identifying significant events, analyzing network states, and implementing countermeasures to ensure timely message delivery and meet performance criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a broker-based pub-sub architecture uses best-effort delivery without traffic differentiation, then the system is simple to operate and has low device complexity, but time-critical traffic cannot be handled effectively and message delivery timing is not guaranteed
Solution Approach 1:
The patent segments message traffic into different priority levels (time-critical and non-time-critical) and processes them through separate queues and delivery mechanisms. The broker divides its message handling into priority-based segments, allowing time-critical messages to be delivered with guaranteed timing while non-time-critical messages use best-effort delivery, thus resolving the contradiction between reliability for time-critical traffic and system simplicity.
Solution Approach 2:
The patent changes the delivery parameter from uniform best-effort delivery to priority-based delivery with different service levels. By introducing priority levels and corresponding delivery guarantees, the system can now provide time-critical message delivery while maintaining simple operation for non-time-critical traffic, effectively resolving the contradiction between reliability improvement and complexity increase.
2Productivity
If the broker treats all messages similarly without traffic differentiation, then the system has low device complexity and is easy to manage, but performance requirements for time-critical applications cannot be met
Solution Approach 1:
The broker segments incoming messages into different priority queues based on their time-critical nature. Time-critical messages are routed to a high-priority queue with guaranteed delivery timing, while non-time-critical messages go to a best-effort queue. This segmentation enables differentiated message processing that improves time-critical delivery speed without requiring complete architectural overhaul.
Solution Approach 2:
The patent introduces a traffic classification intermediary layer between message reception and delivery. This intermediary sorts and prioritizes messages before they enter the delivery pipeline, enabling the broker to handle time-critical traffic with guaranteed performance while maintaining simple handling of other traffic. The intermediary acts as a mediator that adds functionality without significantly increasing overall system complexity.
3Adaptability or versatility
If existing pub-sub systems offload timely delivery responsibility to the communication infrastructure using multicast groups, then the broker remains simple, but the system lacks flexibility for complex filtering and is difficult to set up across different subnetworks
Solution Approach 1:
The patent introduces an orchestrator as an intermediary component that manages complex filtering logic and cross-subnetwork message routing. The orchestrator sits between publishers and brokers, enabling sophisticated topic filtering and subscription management without burdening individual brokers with complex logic. This intermediary approach provides filtering flexibility and cross-subnetwork compatibility while keeping broker implementation simple.
Solution Approach 2:
The patent moves complex filtering and subscription management to a new dimensional layer (the orchestrator layer) above the traditional broker-subscriber model. By elevating these functions to a separate orchestration dimension, the system gains flexibility for complex filtering and cross-subnetwork operation without increasing complexity within the broker layer, effectively resolving the contradiction.
Data Source
AI summary
A method for managing performance in a distributed system with a broker-based publish-subscribe architecture. The method includes: determining at least one performance requirement of the distributed system on the basis of a network state of the distributed system, wherein the network state is specific to a traffic and/or execution performance of the distributed system; identifying a significant event, wherein the significant event describes a change in the distributed system; changing the distributed system on the basis of the significant event; determining a new network state of the changed distributed system; analyzing the new network state with reference to the at least one performance requirement of the distributed system; carrying out at least one countermeasure depending on a result of the analysis. A computer program, a device, and a storage medium are also described.