Enterprise Event Routing for Heterogeneous LOB Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data synchronization techniques for Line of Business (LOB) systems are inefficient, leading to high computing and communication resource costs, particularly due to the use of pull models which result in missed change events and interoperability issues with diverse LOB systems.
Innovation Solution
Implementing an integrated push notification model using a web service with a common addressing scheme and data schema, allowing LOB systems to push notifications to an enterprise system, which routes them to custom event receivers for executing custom business logic, and notifies client devices via various messaging techniques.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a pull model is used for data synchronization, then the enterprise system can retrieve data from LOB systems, but change events may be missed and interoperability issues arise with diverse LOB systems
Solution Approach 1:
The patent inverts the traditional pull model by implementing a push notification model where LOB systems proactively send notifications to the enterprise system. This inversion resolves the contradiction by ensuring reliable data synchronization through push notifications while improving adaptability through a standardized web service interface that can handle diverse LOB systems uniformly
Solution Approach 2:
The patent creates a universal event notification service that can interface with multiple heterogeneous LOB systems through a common web service protocol. This universal interface improves adaptability across diverse systems while maintaining reliable synchronization through standardized push notification mechanisms
2Productivity
If data synchronization operations are performed with high performance, then data freshness is improved, but computing and communication resource costs increase
Solution Approach 1:
The patent implements event-driven periodic action where the enterprise system performs synchronization operations only when change events occur, rather than continuously polling. This approach maintains high data freshness productivity while reducing computing and communication resource costs by eliminating unnecessary periodic operations
Solution Approach 2:
The LOB systems perform self-service by automatically generating and sending push notifications when data changes occur. This eliminates the need for the enterprise system to continuously poll LOB systems, improving synchronization performance while significantly reducing computing and communication resource costs
3Adaptability or versatility
If custom business logic is implemented for each LOB system, then specific application requirements are met, but system complexity increases
Solution Approach 1:
The patent segments custom business logic into separate, independently deployable event receiver components that can be selectively activated. Each custom logic module handles specific LOB system requirements, while the core notification service remains standardized and simple. This segmentation allows adaptability for custom requirements without increasing overall system complexity
Solution Approach 2:
The patent introduces an intermediary event receiver layer that sits between the standardized push notification service and custom business logic. This intermediary component receives standardized notifications and routes them to appropriate custom handlers, enabling adaptability for specific application requirements while maintaining a simple, unified notification interface
Data Source
AI summary
Techniques to manage remote events are described. An apparatus may comprise a processor circuit and a remote event application arranged for execution by the processor circuit. The remote event application may be operative to manage remote event notifications for a publisher entity and a subscriber entity. The remote event application may comprise, among other elements, an event monitor component operative to receive an external event notification message with a publisher entity event for the publisher entity. The event monitor component may select a custom event receiver component associated with the publisher entity from among multiple custom event receiver components, and send the external event notification message to the selected custom event receiver component. The custom event receiver component may implement custom business logic, such as code callouts designed for specific application programs or system programs. Other embodiments are described and claimed.