Event Message Transformation for Multi-Data Center Replication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data replication systems across multiple data centers face challenges in reducing latency, resource consumption, and ensuring failover support while maintaining data consistency and security, particularly in ensuring the safety and security of client information accessed through electronic portals.
Innovation Solution
A computing platform transforms event messages from an authentication hub into multiple topic-specific messages and sends them to different data centers, allowing listening services to detect alerts and manage message queues, with the ability to generate configuration commands for failover support in case of data center failures, thereby optimizing data replication and resource utilization.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data is replicated across multiple data centers using traditional methods, then data consistency and security are maintained, but latency increases and throughput decreases
Solution Approach 1:
The patent segments data replication by creating separate message queues for different data centers and using topic-based routing to distribute event messages to specific queues. This allows parallel processing and reduces contention, thereby reducing latency while maintaining data consistency across segmented replication paths
Solution Approach 2:
The patent introduces an intermediary messaging service that acts as a mediator between the event source and multiple data centers. This messaging service manages message queues, handles routing, and coordinates replication, reducing direct communication overhead and latency while ensuring consistent data distribution
2Reliability
If data is replicated across multiple data centers using traditional methods, then data consistency is ensured, but resource consumption increases
Solution Approach 1:
The patent merges multiple replication operations into a single message queueing and routing system. By consolidating replication logic into the messaging service that handles multiple data centers simultaneously, resource consumption is optimized through shared infrastructure and coordinated processing rather than separate replication mechanisms
Solution Approach 2:
The patent performs preliminary actions by pre-configuring message queues, topics, and routing rules before data replication occurs. Event messages are transformed and routed through predefined paths, reducing computational overhead during actual replication and minimizing resource consumption while maintaining consistency
3Productivity
If data replication is optimized for speed, then latency is reduced and throughput increases, but failover support and system reliability deteriorate
Solution Approach 1:
The patent implements beforehand cushioning by maintaining message queues and replication infrastructure in advance across multiple data centers. These pre-established communication channels and redundant systems are ready to immediately take over if a failure occurs, ensuring both high throughput during normal operation and reliable failover when needed
Solution Approach 2:
The patent implements feedback mechanisms through listening services that monitor message queues and detect events across data centers. This feedback system enables real-time detection of failures and automatic routing adjustments, maintaining both high throughput and reliable failover support through continuous monitoring and adaptive response
Data Source
AI summary
Aspects of the disclosure relate to optimizing data replication across multiple data centers. A computing platform may receive, from an authentication hub computing platform, an event message corresponding to an event associated with the authentication hub computing platform. In response to receiving the event message, the computing platform may transform the event message to produce multiple transformed messages. The multiple transformed messages may include a first transformed message associated with a first topic and a second transformed message associated with a second topic different from the first topic. Subsequently, the computing platform may send, to at least one messaging service computing platform associated with at least one other data center different from a data center associated with the computing platform, the multiple transformed messages. In some instances, the event message may include information identifying a user account login event that occurred at the authentication hub computing platform.


