Global Data Synchronization Reactor for Microservices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current identity management systems lack a global solution to support organizations with employees in multiple countries, leading to difficulties in data synchronization across different geographic regions with varying data privacy regulations, increased costs, and operational risks due to their rigid architecture and lack of single identifiers and single sign-on capabilities.
Innovation Solution
An outbound global data synchronization reactor listens for event messages in a domain message pipeline, applies local data publication rules to generate edited event information, and publishes it to a global message pipeline, ensuring data synchronization across regions while adhering to local privacy regulations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple regional identity solutions are used to support employees in different countries, then local compliance with data privacy regulations is improved, but system complexity and difficulty of interoperability increase
Solution Approach 1:
The patent implements a universal identity management system that serves multiple geographic regions with different data privacy regulations through a single integrated platform. The system uses a common identity provider that can operate in different regions (e.g., US, EU, APAC) while maintaining compliance with local regulations through configurable data handling, eliminating the need for separate regional identity solutions and reducing overall system complexity.
Solution Approach 2:
The patent introduces a data synchronization reactor as an intermediary component that mediates between the central identity management system and regional services. This reactor subscribes to events from the central system, applies local data publication rules to ensure compliance with regional privacy regulations, and publishes adapted events to regional message pipelines, thereby enabling a single system to serve multiple regions without increasing complexity.
2Adaptability or versatility
If siloed regional identity solutions are implemented, then local data privacy compliance is improved, but interoperability across different products deteriorates
Solution Approach 1:
The patent merges previously siloed regional identity solutions into a single unified identity management system. By consolidating identity provisioning, authentication, and authorization functions into one central platform with a common user profile store, the system enables seamless interoperability across different products and services while maintaining compliance with local data privacy regulations through centralized control.
Solution Approach 2:
The data synchronization reactor acts as an intermediary that ensures smooth interoperability between the central identity system and regional services. It subscribes to central events, applies local data publication rules to filter and transform data according to regional privacy requirements, and publishes adapted events to regional message pipelines, thereby maintaining compliance while enabling seamless integration across products.
3Reliability
If rigid monolithic architecture is used in identity management systems, then system stability is improved, but adaptability to new capabilities and upgrades deteriorates
Solution Approach 1:
The patent segments the identity management system into modular microservices that communicate through event-driven architecture. Instead of a rigid monolithic structure, the system is divided into independent services (e.g., identity provider, data synchronization reactor, regional services) that can be developed, deployed, and scaled independently. This segmentation maintains system stability through controlled communication interfaces while significantly improving adaptability to new capabilities and upgrades.
Solution Approach 2:
The patent implements a dynamic event-driven architecture where services communicate through asynchronous event streams rather than rigid synchronous calls. The data synchronization reactor dynamically subscribes to and publishes to event streams based on configuration, allowing the system to adapt to new capabilities and regional requirements without requiring changes to the core architecture. This dynamic approach maintains stability through standardized event interfaces while enabling flexible adaptation.
4Ease of operation
If monolithic identity management systems are used, then operational simplicity is improved, but operational risks and costs increase
Solution Approach 1:
The patent segments the monolithic identity management system into smaller microservices that can be deployed and operated independently. This segmentation reduces operational risks by isolating failures to individual services rather than affecting the entire system, while the event-driven communication layer maintains operational simplicity through standardized asynchronous interactions. Each microservice can be scaled and updated independently, reducing costs associated with maintaining a single large monolithic system.
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.