Microservice Data Restore Through Cross-Database Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing microservice architectures face challenges in consistently restoring data across separate databases and persistencies following disruptive events, leading to inconsistent and inefficient data recovery.
Innovation Solution
A synchronization identification engine is used to verify and restore data record synchronization across multiple data tables by matching record identifiers in an inversed chronological order, enabling recursive synchronizations from the main application to related microservices, and prioritizing data record synchronization based on scopes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate databases are used for each microservice and application, then system modularity and independence are improved, but data consistency and synchronization across services deteriorate
Solution Approach 1:
The system implements a feedback mechanism where the synchronization identification engine continuously monitors data records across microservice databases, identifies inconsistencies, and triggers restoration processes to maintain data consistency while preserving service independence
Solution Approach 2:
A central synchronization identification engine acts as an intermediary between separate microservice databases, coordinating data synchronization and consistency restoration without requiring changes to the individual microservice architectures
2Reliability
If traditional backup and restore processes are used for each database, then data recovery capability is improved, but restoration consistency across microservices deteriorates
Solution Approach 1:
The system merges individual microservice backup and restore processes into a unified coordinated restoration process, where the synchronization identification engine manages simultaneous restoration across multiple databases to ensure consistency
Solution Approach 2:
The system performs preliminary identification of data inconsistencies and restoration requirements before executing the actual restore process, ensuring that all microservices are restored to consistent states simultaneously
3Reliability
If data synchronization verification is performed across all microservices, then data consistency is improved, but system latency and recovery time deteriorate
Solution Approach 1:
The synchronization identification engine performs partial verification by focusing only on affected data records and microservices rather than进行全面 verification of all databases, reducing recovery time while maintaining consistency for critical data
Data Source
AI summary
Methods, systems, and computer-readable storage media for restoring microservice persistencies. A disruptive event potentially affecting a computing system functionality and data synchronization of one or more applications and one or more microservices is determined. Each application and microservice stores respective data records in separate data tables. A restoration of the computing system functionality is determined. A synchronization process is initiated by using a synchronization identification engine. Data record synchronization is verified across a plurality of data tables, by matching record identifiers according to a call mapping between the applications and the microservices. The data record synchronization is restored across the plurality of data tables. An access to the applications and the microservices is reactivated.