Microservice Data Synchronization Using Changeplans and Durable Messaging

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Maintaining data synchronization across a distributed system, such as in a retail environment with cloud-based servers and edge devices, is challenging due to the need for continuous data replication and dynamic updates, while minimizing operational disruptions and allowing for staged roll-outs and different configurations.

Innovation Solution

Implementing a changeplan that specifies microservices data updates, using a microservices architecture to export and import updated data across enterprise and store levels, with durable message buses for offline communication, and supporting multiple configurations through concurrent changeplans.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If continuous data replication is implemented across distributed systems, then data synchronization is improved, but system complexity and operational disruptions increase

Engineering Contradiction:

Improvedata synchronizationVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments data replication into staged roll-outs where changes are deployed incrementally across different store locations rather than simultaneously across the entire distributed system. This allows complex synchronization operations to be broken into manageable segments that can be controlled and monitored individually, reducing overall system complexity while maintaining synchronization reliability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system implements dynamic configuration capabilities that allow different store locations to have different replication configurations and timing. This enables the system to adapt the replication process to local conditions, reducing operational disruptions while maintaining data synchronization across the distributed environment.

Inventive Principle:

Principle #15Dynamics

2Stability of the object's composition

If unified data configuration is enforced across all store locations, then data consistency is improved, but adaptability to local configurations is reduced

Engineering Contradiction:

Improvedata consistencyVSAvoidlocal configuration flexibility

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system applies local quality by allowing each store location to have customized configurations while maintaining core data consistency. Different stores can have different microservice instances with locally-adapted parameters, yet all remain synchronized to the same data model and business rules, achieving both consistency and adaptability simultaneously.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system implements universality through a common data model and synchronization framework that serves all store locations, while allowing local instances to specialize according to specific needs. The microservice architecture enables the same core service to function differently across locations, providing both unified consistency and local versatility.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Productivity

If rapid data updates are implemented, then productivity is improved, but data synchronization reliability deteriorates

Engineering Contradiction:

Improvedata update speedVSAvoidsynchronization reliability

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary actions by preparing and validating data updates before actual replication occurs. Change plans are formulated and approved in advance, allowing the system to stage updates and ensure synchronization reliability before rapid deployment, thus maintaining both speed and reliability.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms that monitor data synchronization status in real-time during rapid updates. This allows the system to detect and correct synchronization issues immediately, maintaining reliability even during high-speed data propagation across the distributed system.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS12488016B2Synchronized data management in a distributed computing environment using microservice architecture

Publication Date: 2025.12.02 TOSHIBA GLOBAL COMMERCE SOLUTIONS HLDG

AI summary

A method of synchronizing data across an enterprise system including enterprise servers on an enterprise level and including store locations at a store level including edge devices operatively coupled to the enterprise servers can be provided by providing a changeplan that specifies updated data for microservice data operating within the enterprise system on an endpoint that utilizes the microservice in a microservice architecture to perform operations at a store location, executing the changeplan to initiate an export from an enterprise server that operates the microservice at the enterprise level to create an updated state for the microservice data on the endpoint, replicating the updated state for the microservice data at the enterprise server to provide an export updated state for the microservice data on the endpoint, storing the export updated state for the microservice data in an export table at the enterprise level, transmitting a message on a durable message bus from the enterprise level to the store level, initiating an import process at a store server responsive to receiving the message on the durable message bus and retrieving the export updated state for the microservice data from the export table.