Cloud Messaging Service Decouples Source and Target Applications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Tightly coupled integration flows in hybrid Software-as-a-Service (SaaS) and on-premises applications require frequent modifications when either application changes, complicating enterprise application integration.
Innovation Solution
A system and method using a messaging service within a cloud-based integration service to decouple source and target applications, allowing them to publish and subscribe to messages independently, enabling synchronization and flexible subscription management without affecting other applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If integration flows map data directly from one application to another, then data integration is achieved, but the applications become tightly coupled requiring frequent modifications when either application changes
Solution Approach 1:
The patent introduces a messaging service as an intermediary component between source and target applications. This messaging service acts as a mediator that receives messages from source applications and delivers them to target applications, thereby decoupling the direct connection between applications. The messaging service handles the integration logic independently, allowing source and target applications to remain unchanged when modifications are needed.
2Speed
If applications are directly integrated through integration flows, then real-time data synchronization is achieved, but any application change requires modification of the integration flow
Solution Approach 1:
The patent segments the integration architecture into independent components: source applications, messaging service, and target applications. Each component operates independently with well-defined interfaces. The messaging service is further segmented into message production, message brokering, and message consumption functions. This segmentation reduces integration flow complexity by eliminating the need for end-to-end configuration and reduces the impact of changes on the overall system.
3Adaptability or versatility
If a messaging service is introduced to decouple applications, then adaptability to changes is improved, but system complexity increases
Solution Approach 1:
The messaging service is designed as a universal platform that can serve multiple source and target applications simultaneously. It provides standardized message production and consumption interfaces that work across different application types and technologies. This multi-functionality reduces overall system complexity by consolidating integration logic into a single reusable component rather than requiring separate integration flows for each application pair.
Data Source
AI summary
In accordance with an embodiment, described herein is a system and method for decoupling a source application and a target application using a messaging service associated with a cloud-based integration service. A first integration flow can be provided to enable the source application or producer to publish messages to the messaging service. A second integration flow can be provided to enable the target application or consumer to subscribe to the messaging service to receive messages. The source application and the target application can be agnostic of each other's implementation details, and those of the messaging service, which effectively decouples the source and target applications. The system enables objects between the source and target applications to be sychronized, multiple applications to subscribe to the integration cloud service and register for updates, and one or more applications to be added or removed as subscribers without affecting other subscribers or producers.