Back to results
US 11,144,529 B2Granted
Consistent data replication in an event-driven architecture
AssigneeSap SE
InventorsBertram Beyer, Niklas Schoenberger, Hans-Christian Kutschujawy
Life of this patent
Estimating the term…
Abstract
In an example embodiment, a replication state database is utilized in conjunction with a version clock to track changes to data in an event-driven architecture. The replication state database then can be used to ensure data consistency of the data. Opportunistic Concurrency Control can also be utilized to allow for parallel processing by instances.
Claims20
A system comprising:
- at least one hardware processor;
- and
- a computer-readable medium storing instructions that, when executed by the at least one hardware processor, cause the at least one hardware processor to perform operations comprising:
- receiving, at a first data consumer, a first event pertaining to a first piece of data stored in a local database, the first event generated by a data producer and including metadata comprising an identification in an identification field and a version clock value in a version clock field;
- in response to the receiving, accessing a replicated data table shared with a second data consumer, to identify a current version clock value for the first piece of data;
- determining that the version clock value in the metadata of the first event is less than the current version clock value for the first piece of data from the replicated data table;
- and
- in response to the determining, discarding the first event without changing the local database to reflect the first event.
5 more elements
A method comprising:
- receiving, at a first data consumer, a first event pertaining to a first piece of data stored in a local database, the first event generated by a data producer and including metadata comprising an identification in an identification field and a version clock value in a version clock field;
- in response to the receiving, accessing a replicated data table shared with a second data consumer, to identify a current version clock value for the first piece of data;
- determining, using a hardware processor, that the version clock value in the metadata of the first event is less than the current version clock value for the first piece of data from the replicated data table;
- and
- in response to the determining, discarding the first event without changing the local database to reflect the first event.
2 more elements
A non-transitory machine-readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations comprising:
- receiving, at a first data consumer, a first event pertaining to a first piece of data stored in a local database, the first event generated by a data producer and including metadata comprising an identification in an identification field and a version clock value in a version clock field;
- in response to the receiving, accessing a replicated data table shared with a second data consumer, to identify a current version clock value for the first piece of data;
- determining that the version clock value in the metadata of the first event is less than the current version clock value for the first piece of data from the replicated data table;
- and
- in response to the determining, discarding the first event without changing the local database to reflect the first event.
2 more elements
Dependencies are inferred from the claim text.