Event Clearinghouse Mediator for Cloud Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex, multi-vendor electronic data storage systems face challenges in managing event notifications effectively, as existing solutions often require impractical customization and lack flexibility in handling diverse user needs and vendor-specific configurations.
Innovation Solution
The system collects events and modifies their disposition using component-specific indicators, with hierarchical rule mapping tables that allow per-vendor, per-tenant, and mode-specific instructions, enabling dynamic updates and coordinated event processing across a networked environment.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If components in complex multi-vendor systems process events independently according to their own configurations, then each component can operate autonomously with its own event handling logic, but the system lacks coordinated event management and cannot tailor event processing to different user needs and system modes
Solution Approach 1:
An event clearinghouse is introduced as an intermediary component that receives events from multiple vendor components, applies disposition rules, and routes events appropriately. This mediator coordinates event processing across the multi-vendor system without requiring customization of the original components, resolving the contradiction by enabling centralized control while maintaining component autonomy.
Solution Approach 2:
The event processing system is segmented into distinct functional layers: event collection from components, rule-based disposition modification in the clearinghouse, and targeted event routing. This segmentation allows each layer to operate independently with specialized logic, enabling adaptable event processing while managing system complexity through modular architecture.
2Ease of operation
If customized reprogramming of components is performed to achieve desired event processing, then event handling can be precisely tailored to system needs, but customization becomes impractical and increases implementation complexity
Solution Approach 1:
The event clearinghouse serves as an intermediary that provides disposition rules without modifying the original components. This allows event processing to be customized through configurable rules in the clearinghouse rather than through component reprogramming, making customization practical and manageable while maintaining ease of operation.
Solution Approach 2:
Disposition rules in the event clearinghouse are made dynamic and configurable, allowing the system to adapt event processing behavior without permanent component modifications. This dynamic rule-based approach enables easy customization and updates of event handling logic independent of the underlying components.
3Reliability
If a centralized event processing system is implemented to coordinate all events, then systematic event management is achieved, but the system becomes less flexible in handling vendor-specific and tenant-specific requirements
Solution Approach 1:
The event clearinghouse applies different disposition rules to events based on their source, tenant, and system mode. Each event receives customized processing appropriate to its specific context while still passing through the centralized clearinghouse for coordinated management. This local quality approach maintains both centralized reliability and vendor-specific adaptability.
Solution Approach 2:
The system changes processing parameters (disposition rules) dynamically based on event characteristics, vendor identity, tenant requirements, and system mode. This parameter-based flexibility allows the centralized clearinghouse to adapt its behavior to specific vendor and tenant needs while maintaining overall systematic control and reliability.
Data Source
AI summary
An event clearinghouse engine is used with a data storage system to modify event disposition associated with components. A separate component disposition table is provided for each component. The component disposition table specifies different sets of disposition modifications for different types of events as indicated by event ID. A global disposition rule mapping table includes disposition modifications which are applied to all events. Per-vendor and per-tenant tables may be used to specify disposition modifications for particular vendors and tenants. Mode-specific tables such as a rescue/recovery mode table may be used to specify disposition modifications when the storage system is in a particular mode. The tables may be implemented in stages, including parallel and serial application.