Microservices to Monolith Data Syncback via Mapping ID
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions fail to provide a unified framework for synchronizing data back to monolithic applications on mainframe platforms, especially with microservices architecture, due to heterogeneity of databases and lack of viable products for Mainframe IMS, leading to increased time to market and technical debt.
Innovation Solution
A platform and language agnostic data sync back solution module that enables both synchronous and asynchronous data delivery, capable of synchronizing data with Mainframe IMS databases, using APIs to update source and target databases, and generating mapping identifiers for data synchronization across different platforms and systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If microservices architecture is used to enable agile development and independent deployment, then development flexibility and deployment speed are improved, but data synchronization complexity and time to market increase due to heterogeneity of databases and lack of unified framework
Solution Approach 1:
The patent implements a universal data synchronization framework that can work with multiple database types (DB2, IMS, Oracle, MySQL, MongoDB) and microservice platforms (AWS, Azure, GCP, on-premise) through a single unified architecture. The framework provides database-agnostic data capture, transformation, and synchronization capabilities that eliminate the need for separate synchronization solutions for each database type, thereby reducing time to market while maintaining adaptability across heterogeneous environments.
Solution Approach 2:
The patent introduces an intermediary data synchronization layer that sits between microservices and mainframe systems. This intermediary framework captures data changes at the source, transforms them into a standardized format, and delivers them to target systems. The intermediary approach abstracts the complexity of direct database-to-database synchronization, enabling agile microservice development while maintaining efficient data synchronization across diverse platforms.
2Reliability
If conventional CDC solutions are used for data synchronization, then data capture capability is improved, but adaptability to modern multi-database and multi-platform architectures deteriorates
Solution Approach 1:
The patent creates a universal data synchronization framework that replaces conventional CDC solutions with a database-agnostic approach. The framework can capture data changes from any database type (relational, NoSQL, cloud-based, on-premise) and deliver them to any target system. This universal capability maintains reliable data capture while extending compatibility to modern multi-database and multi-platform architectures that conventional CDC solutions cannot support.
Solution Approach 2:
The patent changes the fundamental parameters of data synchronization by moving from database-specific CDC protocols to a unified, parameter-agnostic synchronization model. The framework allows configuration of data capture and delivery parameters without being constrained by specific database vendor protocols, enabling seamless adaptation to emerging database technologies and platforms while maintaining proven data capture reliability.
3Adaptability or versatility
If each microservice develops its own data synchronization solution, then service independence is improved, but system complexity and technical debt increase
Solution Approach 1:
The patent segments the data synchronization function into independent, reusable components that can be consumed by individual microservices while maintaining a unified overall solution. Each microservice can independently configure and use the synchronization framework according to its specific needs, preserving service independence. Meanwhile, the segmented architecture prevents complexity multiplication because all services share the same underlying synchronization engine rather than each implementing its own complete solution.
Solution Approach 2:
The patent enables microservices to self-configure data synchronization through declarative configuration files and automated service discovery. Each microservice can independently declare its data synchronization requirements, and the framework automatically configures the appropriate synchronization behavior. This self-service approach maintains service independence while eliminating the need for complex custom synchronization code in each service, thereby reducing overall system complexity and technical debt.
Data Source
AI summary
Various methods, apparatuses/systems, and media for data migration readiness of a target data source are disclosed. A processor invokes, in response to triggering a process, an application programming interface (API) to call corresponding source application or microservice hosted on a source database; updates, by the source application or microservice, the source database to reflect the changes made to one or more fields data of user profile; generates a mapping identifier (ID) in response to updating the source database; stores the mapping ID onto a mapping database in a predefined format; invokes another API call to obtain source table field details of the updated source database and the mapping ID that maps source column of the source table to a corresponding target column of a target table of a target database; and automatically updates the target database to match the updated data of the source database based on the mapping ID.