Throttled Message Flow for Enterprise Backend Protection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprise backend systems face bottlenecks due to peak inbound message traffic, which can be costly to address through infrastructure upgrades or changes to legacy systems.
Innovation Solution
A system that uses a fault-tolerant message broker and a throttling mechanism to regulate message flow by accumulating messages in buckets and shipping them at a rate aligned with the backend system's capabilities, implemented using Kafka-like messaging systems with a throttler daemon to manage message buckets and optimize outbound traffic.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If the enterprise backend system processes real-time message streams directly, then message processing speed is maintained, but the system becomes vulnerable to peak traffic bottlenecks
Solution Approach 1:
The patent applies preliminary action by pre-allocating message buckets and establishing the throttling mechanism before peak traffic occurs. The message broker is configured with bucket templates that define maximum storage sizes and threshold values in advance, allowing the system to smoothly transition into peak traffic handling without reactive changes.
Solution Approach 2:
The patent introduces a message broker as an intermediary component between the message stream source and the enterprise backend system. This broker accumulates messages in buckets and regulates their release rate, acting as a buffer that decouples the high-speed message ingress from the slower backend processing capacity, thereby protecting the system from peak traffic while maintaining processing speed.
2Productivity
If backend infrastructure is upgraded to handle peak inbound message traffic, then system capacity is improved, but infrastructure cost increases
Solution Approach 1:
The patent creates virtual copies of processing capacity through message buckets that can be dynamically allocated and scaled. Instead of permanently upgrading infrastructure, the system uses software-based bucket templates that can be instantiated as needed, providing scalable capacity without proportional increases in physical infrastructure resources.
Solution Approach 2:
The patent changes the operational parameters of the messaging system by introducing configurable bucket templates with adjustable maximum storage sizes, threshold values, and shipping rates. These parameter changes allow the system to adapt its message handling capacity dynamically without requiring infrastructure upgrades, optimizing resource utilization across different traffic conditions.
3Productivity
If message accumulation buckets are implemented, then traffic throttling is achieved, but message storage requirements increase
Solution Approach 1:
The patent implements dynamic message bucket templates that can adjust their storage capacity and threshold values based on traffic conditions and backend system capabilities. The buckets transition between different states (empty, accumulating, shipping) based on configurable thresholds, allowing the storage volume to be dynamic rather than static, optimizing the balance between throttling effectiveness and storage requirements.
Data Source
AI summary
An enterprise backend system may have inherent limits on a throughput of inbound messages. In one implementation, a message producer publishes messages to a message broker at a high throughput. A message consumer receives messages from the broker and throttles the throughput of messages shipped to an enterprise backend system.