IP Library Granted Patent US 11,645,302
Granted Patent B2
US 11,645,302 · App. 17/025,172 · Granted May 9, 2023

Methods and systems providing synchronization of data in a distributed system using microservice architecture in servers, store controllers, terminals and related articles of manufacture

Inventors: Zachary McCain Darden (New Hill, NC); Jonathan Waite (Cary, NC); Andrew Wesley Norris (Durham, NC); Valentin Mourzenok (Chapel Hill, NC)
Assignee: Toshiba Global Commerce Solutions Holdings Corporation
G06F16/27G06Q10/10H04L67/1095
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,645,302
App. No.
17/025,172
Granted
May 9, 2023
Kind
B2
Abstract

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.

Claims (37)

1. A method of synchronizing data across an enterprise system, the method comprising:

providing a changeplan to an enterprise server associated with an enterprise system, the enterprise system comprising an enterprise level and a group of endpoints at a store level, wherein the changeplan specifies updated data for a microservice operating within the enterprise system on each endpoint among the group of endpoints at the store level, wherein each endpoint utilizes the microservice to perform operations within the enterprise system at the store level;

executing the changeplan to initiate an export operation from the enterprise server;

responsive to initiating the export operation from the enterprise server, generating an updated state for the microservice;

replicating the updated state for the microservice at the enterprise server;

providing an export updated state based on the replicated updated state for the microservice;

storing the export updated state in an export table at the enterprise level;

transmitting a message on a durable message bus from the enterprise level to the store level indicating that the export operation is complete, wherein the message is made persistently available on the durable message bus such that an offline endpoint can receive the message when the offline endpoint comes online;

initiating an import process at the store level responsive to receiving the message on the durable message bus; and

retrieving the export updated state for the microservice from the export table.

2. The method of claim 1 wherein providing the changeplan further comprises:

providing a first changeplan that specifies first updated data for the microservice operating within the enterprise system on a first endpoint that utilizes the microservice to perform operations; and

providing a second changeplan that specifies second updated data for the microservice operating within the enterprise system on a second endpoint that utilizes the microservice to perform operations.

3. The method of claim 2 wherein the first changeplan defines the first updated data for the microservice relative to a production version of the microservice and the second changeplan defines the second updated data for the microservice relative to the production version.

4. The method of claim 3 wherein the first updated data is different than the second updated data.

5. The method of claim 2 wherein the first changeplan defines the first updated data for the microservice relative to a production version of the microservice and the second changeplan defines the second updated data for the microservice relative to the first updated data.

6. The method of claim 5 wherein executing the changeplan further comprises:

executing the first changeplan to initiate an export from the enterprise server that operates the microservice at the enterprise level to create a first updated state for the microservice on the first endpoint relative to a production version of the microservice; and then

executing the second changeplan to initiate an export from the enterprise server that operates the microservice at the enterprise level to create a second updated state for the microservice on the second endpoint relative to the first updated data.

7. The method of claim 1 wherein executing the changeplan further comprises:

executing the changeplan to initiate the export operation from the enterprise server that operates the microservice at the enterprise level to create a delta updated state for the microservice on a first endpoint, wherein the delta updated state comprises less than a full state updated state for the microservice on the first endpoint and includes additions to and deletions from the microservice relative to a production version of the microservice.

8. The method of claim 7 wherein executing the changeplan further comprises:

executing the changeplan to initiate the export operation from the enterprise server that operates the microservice at the enterprise level to create a full updated state for the microservice on the first endpoint, wherein the full updated state and the delta updated state are maintained in the export table.

9. The method of claim 8 wherein retrieving the export updated state comprises retrieving a full export updated state or a delta export updated state for the microservice from the export table.

10. The method of claim 1 wherein initiating the import process at the store level further comprises:

receiving a request for the export updated state for the microservice on a first endpoint at the enterprise server; and

generating a delta updated state for the microservice on the first endpoint responsive to the request if a size of a full updated state is greater than a delta updated state, wherein the delta updated state comprises less than a full state updated state for the microservice on the first endpoint and includes additions to and deletions from the microservice relative to a production version of the microservice.

11. A non-transitory computer-readable medium whose contents, when executed by a computing system, cause the computing system to perform operations for 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 comprising:

synchronizing data across an enterprise system, wherein the enterprise system comprises an enterprise level and a group of endpoints at a store level including edge devices operatively coupled to an enterprise servers, wherein each endpoint utilizes a microservice to perform operations within the enterprise system at the store level, the method comprising:

providing a changeplan to the enterprise server, wherein the changeplan specifies updated data for the microservice operating within the enterprise system on each endpoint among the group of endpoints at the store level;

executing the changeplan to initiate an export operation from an enterprise server;

responsive to initiating the export operation from the enterprise server, generating an updated state for the microservice;

replicating the updated state for the microservice at the enterprise server;

storing the export updated state in an export table at the enterprise level;

transmitting a message on a durable message bus from the enterprise level to the store level indicating that the export operation is complete, wherein the message is made persistently available on the durable message bus such that an offline endpoint can receive the message when the offline endpoint comes online;

initiating an import process at the store level responsive to receiving the message on the durable message bus; and

retrieving the export updated state for the microservice from the export table.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 18, 2020
From: DARDEN, ZACHARY MCCAIN; WAITE, JONATHAN; NORRIS, ANDREW WESLEY; MOURZENOK, VALENTIN
To: TOSHIBA GLOBAL COMMERCE SOLUTIONS HOLDINGS CORPORATION
Reel/Frame 053818/0719 →
Continuity (1)
Related Publication 20220092077A1 · Mar 24, 2022