Cross-Account Event Rule Processing Without Redundant Re-Sends
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing event processing systems process events in a siloed fashion without coordination, leading to inefficiencies and wasteful data processing, especially in cross-account scenarios, which require redundant data handling and risk invocation loops.
Innovation Solution
Implement a system where events for a first account are processed using rules associated with that account, allowing for cross-account delivery by fetching and processing rules for the target account without re-sending events through the initial process, and incorporating mechanisms to detect and prevent invocation loops.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If events are processed separately for each account in siloed fashion, then account isolation and security are maintained, but processing efficiency deteriorates and redundant data handling occurs
Solution Approach 1:
The patent merges event processing across multiple accounts by having the first account's event processing system directly invoke and execute the second account's event processing logic without returning events to the original event bus. This combination eliminates redundant processing while maintaining account isolation through controlled rule-based event routing between accounts.
2Reliability
If cross-account event delivery is implemented by re-sending events through the initial process, then account-specific rule processing is ensured, but data traffic increases and invocation loops risk arises
Solution Approach 1:
The patent extracts the event processing logic from the centralized event bus and implements it directly in the target account's processing system. By taking out the rule execution from the common event bus pathway, the system avoids redundant event transmission while ensuring that account-specific rules are properly applied through direct rule evaluation in the target account context.
3Adaptability or versatility
If multiple hop cross-account delivery is supported, then event routing flexibility is improved, but system complexity and loop detection requirements increase
Solution Approach 1:
The patent applies preliminary action by implementing loop detection mechanisms before events can circulate indefinitely. The system tracks event processing paths and identifies potential invocation loops in advance, preventing infinite circulation while maintaining flexible multi-hop cross-account delivery capabilities through controlled event routing.
Data Source
AI summary
Implementations for providing event processing services that associate multiple accounts are described. A user of a first account may have rules for event processing that cause the event to be sent to a second account. If a received event satisfies the rule, the event may be processed for the first account and processed for the second account using a single processing node and/or single rule evaluation sequence.