Keyed Event Queue Segments Orders to Prevent Blocking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional order platform ecosystems face issues such as Head-of-Line blocking, where failed events can prevent subsequent events from being processed, and a fixed scale that cannot accommodate changes in the number of consumers without disrupting existing orders.
Innovation Solution
The introduction of a keyed event queue (KEQ) message broker, which provides horizontal scalability, low-latency message delivery, and transactional enqueuing, ensuring message processing exclusivity through explicit leases and allowing independent processing of events across separate queues.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If events are processed sequentially in a single queue, then ordering is maintained, but Head-of-Line blocking occurs where failed events prevent subsequent events from being processed
Solution Approach 1:
The patent segments the single event queue into multiple independent queues, each associated with a specific order identifier. This allows events from different orders to be processed in parallel without blocking each other, eliminating Head-of-Line blocking while maintaining order-level sequencing. Each queue operates independently, so failures in one queue do not propagate to other queues.
2Adaptability or versatility
If a fixed scale is used for the message broker, then existing consumers are served, but the system cannot accommodate changes in consumer numbers without breaking ordering
Solution Approach 1:
The patent implements dynamic scaling by allowing the number of queues to be adjusted based on consumer requirements. The system can create, delete, or replicate queues as needed without affecting existing orders. Each queue maintains its own independent ordering guarantee, so scaling operations do not disrupt ongoing event processing or break ordering for existing consumers.
3Productivity
If events from different orders are interleaved into a single queue, then resource utilization is optimized, but consumers must process events sequentially per partition causing blocking
Solution Approach 1:
The patent divides the event stream into separate queues based on order identifiers, allowing consumers to process events from different orders in parallel. Each consumer can independently process events in its assigned queue without waiting for other queues, simplifying the processing operation while maintaining resource utilization efficiency through parallel processing.
Data Source
AI summary
Keyed Event Queue (KEQ) is a multi-region, dynamically-scaled message broker for managing a large number of independent strictly-ordered message queues. In this regard, a first request having a first plurality of associated events may be enqueued in a first queue, while a second request having a second plurality of associate events is enqueued in the second queue. The first and second queues are processed independently, such that any issues or failures that may arise with respect to the first plurality of events do not block the second plurality of events from being executed.