Enterprise Service Bus for Event-Driven Data Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems for data synchronization in computer data centers, such as cloud services, face inefficiencies and inconsistencies when updating information across multiple business applications, as they rely on point-to-point integration and specialized connections, leading to data inconsistencies over time.
Innovation Solution
A computer processing platform with an enterprise service bus (ESB) manages the exchange and sharing of business data between applications by receiving object data from one application instance, updating a database, applying transformation policies if necessary, identifying relevant clients for updates, and communicating updated data based on stored preferences and agreements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If point-to-point integration is used for data synchronization between business applications, then data can be shared between applications, but data inconsistencies occur over time and integration complexity increases
Solution Approach 1:
The patent introduces an enterprise service bus (ESB) as a centralized intermediary component that mediates data exchange between multiple business applications. The ESB receives object data from any application instance, applies transformation policies, and distributes updated data to all subscribed applications. This mediator architecture eliminates the need for complex point-to-point integration connections while ensuring data consistency across all applications through centralized control and standardised data exchange protocols.
2Adaptability or versatility
If specialized connections are established between applications for data sharing, then data exchange is enabled, but bandwidth requirements and data transfer overhead increase
Solution Approach 1:
The patent merges multiple separate data exchange connections into a single centralized ESB infrastructure. Instead of establishing individual specialized connections between each pair of applications, all applications connect to the ESB which consolidates data exchange operations. The ESB receives object data from any application instance and distributes it to all subscribed applications, eliminating redundant data transfers and reducing overall bandwidth consumption while maintaining universal data sharing capability.
3Productivity
If multiple applications independently manage common information, then each application has autonomy, but repetitive data entry and data synchronization overhead increase
Solution Approach 1:
The patent enables applications to self-service data synchronization through the ESB without requiring manual intervention or repetitive data entry. When any application instance creates or updates an object, it automatically publishes the object data to the ESB. The ESB then automatically distributes the updated data to all subscribed applications based on stored preferences and client agreements. This self-service mechanism eliminates repetitive data entry and reduces synchronization time while maintaining application autonomy.
Data Source
AI summary
A computer implemented method for updating and distributing data objects among multiple client applications is described. The method includes receiving object data for an object from a first application instance of an application engine, wherein the object data reflects a change to a state of the object based on action of the first application instance, updating a data structure for the object in a based on the received object data, determining whether a transformation policy is applicable to the object and, if so, modifying data associated with the object according to the transformation policy, identifying application instances that should receive updated object data for the object based on stored information identifying clients that have agreed to share updated object data and based on stored information identifying types of updates that clients are to receive, and communicating updated object data to the application instances that should receive updated object data according to stored preferences associated with each of the application instances.