Data synchronization in a cloud infrastructure
US-2016070772-A1 · Mar 10, 2016 · US
US9734224B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9734224-B2 |
| Application number | US-201514664528-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 20, 2015 |
| Priority date | Sep 7, 2012 |
| Publication date | Aug 15, 2017 |
| Grant date | Aug 15, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A synchronization infrastructure that synchronizes data stored between components in a cloud infrastructure system is described. A first component in the cloud infrastructure system may store subscription information related to a subscription order which may in turn be utilized by a second component in the cloud infrastructure system to orchestrate the provisioning of services and resources for the order placed by the customer. The synchronization architecture utilizes transactionally consistent checkpoints that describe the state of the data stored in the components to synchronize the data between these components.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: for a source table in a first computing device comprised in a computing infrastructure system, the source table comprising a plurality of rows, each row of the plurality of rows associated with a checkpoint number, determining, based upon a first checkpoint number associated with the source table and checkpoint numbers associated with the plurality of rows in the source table, a set of one or more rows of the source table that have changed since when the source table was last synchronized with a corresponding target table; determining a first run number associated with the source table, the first run number indicative of a number of data synchronization runs performed for the source table; determining a second run number for the source table based at least in part on determining that the set of one or more rows of the source table have changed; associating, by the first device, the second run number with the source table instead of the first run number; and transferring, by the first device, the set of one or more rows to a target table in a second computing device and associating each row of the set of one or more rows in the target table with the second run number. 2. The method of claim 1 , wherein determining the set of one or more rows that have changed comprises identifying the checkpoint numbers associated with the plurality of rows in the source table that are greater than the first checkpoint number. 3. The method of claim 2 , further comprising determining a second checkpoint number, wherein determining the second checkpoint number comprises identifying a row in the set of one or more rows with a highest checkpoint number. 4. The method of claim 3 , further comprising associating the second checkpoint number with the source table instead of the first checkpoint number. 5. The method of claim 3 , wherein determining the second run number for the source table is further based on identifying the row in the set of one or more rows with the highest checkpoint number. 6. The method of claim 1 , wherein transferring the set of one or more rows to the target table further comprises transferring a new run time associated with each row of the set of one or more rows to the target table. 7. The method of claim 6 , further causing by the first computing device to store the second run number and the new run time in a runs table associated with the target table. 8. A system comprising: one or more computing devices configurable to provide one or more services; a memory configurable to store a subscription order related to the one or more services provided by the system; and wherein a first computing device from the one or more computing devices is configurable to: identify a source table in the first computing device, the source table comprising a plurality of rows, each row of the plurality of rows associated with a checkpoint number; determine based upon a first checkpoint number associated with the source table and checkpoint numbers associated with the plurality of rows in the source table, a set of one or more rows of the source table that have changed since when the source table was last synchronized with a corresponding target table; determine a first run number associated with the source table, the first run number indicative of a number of data synchronization runs performed for the source table; determine a second run number for the source table based at least in part on determining that the set of one or more rows of the source table have changed; associate the second run number with the source table instead of the first run number; and transfer the set of one or more rows to a target table in a second computing device and associate each row of the set of one or more rows in the target table with the second run number. 9. The system of claim 8 , wherein the first computing device is further configured to determine the set of one or more rows that have changed by identifying the checkpoint numbers associated with the plurality of rows in the source table that are greater than the first checkpoint number. 10. The system of claim 9 , wherein the first computing device is further configured to determine a second checkpoint number, wherein the second checkpoint number is determined based on identifying a row in the set of one or more rows with a highest checkpoint number. 11. The system of claim 10 , wherein the first computing device is further configured to associate the second checkpoint number with the source table instead of the first checkpoint number. 12. The system of claim 10 , wherein the first computing device is further configured to determine the second run number for the source table based on identifying the row in the set of one or more rows with the highest checkpoint number. 13. The system of claim 8 , wherein the first computing device is further configured to transfer a new run time associated with each row of the set of one or more rows to the target table. 14. The system of claim 13 , wherein the first computing device is further configured to store the second run number and the new run time in a runs table associated with the target table. 15. A non-transitory computer-readable memory storing a plurality of instructions executable by one or more processors, the plurality of instructions comprising: instructions that cause at least one processor from the one or more processors to identify a source table in a first computing device, the source table comprising a plurality of rows, each row of the plurality of rows associated with a checkpoint number; instructions that cause at least one processor from the one or more processors to determine based upon a first checkpoint number associated with the source table and checkpoint numbers associated with the plurality of rows in the source table, a set of one or more rows of the source table that have changed since when the source table was last synchronized with a corresponding target table; instructions that cause at least one processor from the one or more processors to determine a first run number associated with the source table, the first run number indicative of a number of data synchronization runs performed for the source table; instructions that cause at least one processor from the one or more processors to determine a second run number for the source table based at least in part on determining that the set of one or more rows of the source table have changed; instructions that cause at least one processor from the one or more processors to associate the second run number with the source table instead of the first run number; and instructions that cause at least one processor from the one or more processors to transfer the set of one or more rows to a target table in a second computing device and associate each row of the set of one or more rows in the target table with the second run number. 16. The non-transitory computer-readable memory of claim 15 , further comprising instructions that cause at least one processor from the one or more processors to determine the set of one or more rows that have changed by identifying the checkpoint numbers associated with the plurality of rows in the source table that are greater than the first checkpoint number. 17. The non-transitory computer-readable memory of claim 16 , further comprising instructions that cause at least one processor from the one or more processors to determine a second checkpoint number by identifying a row in the set of one or more rows with a highest checkpoint
Needs-based resource requirements planning or analysis · CPC title
Admission control; Resource allocation · CPC title
Physics · mapped topic
Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title
replenishment orders; recurring orders · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.