Priority Event Queue Routing for Low-Latency Record Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large websites processing millions of events daily face significant latency issues due to the slow processing of event data, particularly for high-priority events like trait events, which are essential for real-time personalized experiences.

Innovation Solution

Implementing a system with multiple queues (priority and standard) and an event manager that segregates events based on type and priority, directing high-priority events to dedicated worker nodes for faster processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If all events are processed through a single queue, then system complexity is reduced, but processing latency increases for high-priority events

Engineering Contradiction:
Improvesystem complexityVSAvoidprocessing latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments the event processing system into multiple queues (high-priority queue and standard queue) based on event priority. High-priority events such as trait events are routed to a dedicated high-priority queue with dedicated worker nodes, while standard events use a separate queue. This segmentation allows high-priority events to be processed independently without being blocked by lower-priority events, thereby reducing processing latency while maintaining manageable system complexity through structured organization.

Inventive Principle:
Principle #1Segmentation

2Speed

If multiple queues and worker nodes are implemented, then processing speed for high-priority events improves, but system complexity increases

Engineering Contradiction:
Improveprocessing speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent applies local quality by providing differentiated processing resources based on event priority. High-priority events receive dedicated worker nodes and a separate queue with higher processing capacity and priority, while standard events use remaining resources. This localized optimization ensures that critical events get the speed they need without requiring the entire system to be over-provisioned, balancing processing speed improvements with controlled system complexity.

Inventive Principle:
Principle #3Local quality

3Reliability

If high-priority events are processed separately, then real-time user experience improves, but resource allocation complexity increases

Engineering Contradiction:
Improvereal-time user experienceVSAvoidresource allocation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements preliminary action by pre-establishing separate high-priority queues and dedicated worker nodes before events arrive. The event routing logic is configured in advance to automatically direct high-priority events (identified by event type such as trait events) to the appropriate queue based on predefined priority criteria. This preliminary setup eliminates the need for complex real-time resource allocation decisions, ensuring reliable real-time processing while keeping resource management straightforward through predetermined rules.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12517772B2Event processing systems and methods
Publication Date: 2026.01.06 ATLASSIAN PTY LTD
  • US12517772B2 patent drawing
  • US12517772B2 patent drawing
  • US12517772B2 patent drawing

AI summary

Systems and methods for processing event records are disclosed. The method includes receiving, at a server node, an event record. The event record includes an event type identifier. The method further includes selecting a message queue from a plurality of message queues for the event record based at least on the event type identifier of the event record, and communicating the event record to the selected message queue. A worker node associated with the selected message queue retrieves the event records, processes it and communicates the processed event record to a downstream service for consumption.