Event Message Pipeline for Loose Coupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing human capital management systems face challenges in effectively communicating event information across multiple applications, leading to inefficiencies and tight coupling between applications, which hinders scalability and resiliency.
Innovation Solution
A publication and subscription model is implemented for event information communication between applications, allowing an application to publish event messages to an event message pipeline, enabling loose coupling and independent deployment of applications, with event listeners receiving and acting upon these messages.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional event communication methods are used between applications, then applications can perform coordinated actions, but the system suffers from tight coupling between applications which hinders scalability and resiliency
Solution Approach 1:
The patent introduces an event message pipeline as an intermediary component that decouples applications from direct communication. Applications publish event messages to the pipeline without knowing which applications will consume them, and consuming applications subscribe to events without direct knowledge of publishers. This mediator pattern resolves the technical contradiction by enabling reliable event-driven communication while eliminating tight coupling between applications.
2Productivity
If applications are tightly coupled for effective event communication, then coordinated actions can be performed, but scalability is hindered due to the need for direct integration between all applications
Solution Approach 1:
The patent segments the monolithic event communication architecture into independent, loosely-coupled components. Each application operates independently, publishing events to the pipeline and subscribing to relevant events without requiring direct integration with other applications. This segmentation enables individual applications to be developed, deployed, and scaled independently while maintaining coordinated actions through shared event subscriptions.
Solution Approach 2:
The event message pipeline serves as a universal communication infrastructure that all applications can use simultaneously. Instead of creating dedicated communication channels between each pair of applications, the pipeline provides a universal publish-subscribe mechanism that any application can utilize, enabling scalability while maintaining coordination efficiency.
3Loss of information
If direct application-to-application communication is used, then event information can be transmitted, but integration complexity increases and ease of integration decreases
Solution Approach 1:
The event message pipeline acts as a standardized intermediary that simplifies integration. Applications interact with the pipeline through uniform publish and subscribe operations, eliminating the need for complex point-to-point integration logic. The pipeline handles message routing, delivery, and formatting, reducing integration complexity while ensuring complete event information transmission.
Data Source
AI summary
A system and method for communicating events between applications. A first application receives event information for an event. A first action is performed by the first application in response to receiving the event information. The first application generates an event message comprising an event name and a message payload. The message payload comprises at least a portion of the event information. The first application publishes the event message by sending the event message to an event message pipeline. A second application may listen for the event message in the event message pipeline, receive the event message from the event message pipeline, and use the message payload to perform a second action, wherein the second action is different from the first action.