Back to results
US 2026/0064666 A1Published application
High-volume operations on document store
AssigneeSap SE
InventorRohit DWIVEDI
Life of this patent
Estimating the term…
Abstract
Systems and methods include a first service to receive events from a first event log, a second service to receive events from a second event log, and a third service to receive events from both event logs. The first event log receives low event volumes and the second event log receives high event volumes. The first service and the second service update a document database based on events associated with non-priority data objects and the third service updates the document database based on events associated with priority data objects. More computing resources are employed to execute the third service than to execute the first service or the second service.
Claims20
A system comprising:
- a document database;
- a first service executable to:
- receive first events from a first event log, each first event associated with a data object and an operation on an instance of the data object;
- determine that a type of a first data object of one of the first events is not a priority data object type;
- and
- in response to the determination that the type of the first data object of the one of the first events is not a priority data object type, update a first one or more documents of the document database based on a first operation of the one of the first events, the updating including updating fields of the first one or more documents as specified in the operation associated with the first event;
- a second service executable to:
- receive second events from a second event log, each second event associated with a data object and an operation on an instance of the data object;
- determine that a type of a first data object of one of the second events is not a priority data object type;
- and
- in response to the determination that the type of the first data object of the one of the second events is not a priority data object type, update a second one or more documents of the document database based on a second operation of the one of the second events, the updating including updating fields of the second one or more documents as specified in the operation associated with the second event;
- and
- a third service executable to:
- receive the first events from the first event log and the second events from the second event log;
- determine that a type of a third data object of one of the first events is a priority data object type;
- in response to the determination that a type of the third data object of the one of the first events is a priority data object type, update a third one or more documents of the document database based on a third operation of the one of the first events, the updating including updating fields of the third one or more documents as specified in the operation associated with the first event;
- determine that a type of a fourth data object of one of the second events is a priority data object type;
- and
- in response to the determination that the type of fourth data object of the one of the second events is a priority data object type, update a fourth one or more documents of the document database based on a fourth data operation of the one of the second events, the updating including updating fields of the fourth one or more documents as specified in the operation associated with the second event.
16 more elements
A method comprising:
- receiving first events at a first service from a first event log, each first event associated with a data object and an operation on an instance of the data object;
- determining, at the first service, that a type of a first data object of one of the first events is not a priority data object type;
- in response to determining that the type of the first data object of the one of the first events is not a priority data object type, updating, by the first service, a first one or more documents of a document database based on a first operation of the one of the first events, the updating including fields of the first one or more documents as specified in the operation associated with the first event;
- receiving second events at a second service from a second event log, each second event associated with a data object and an operation on an instance of the data object;
- determining, at the second service, that a type of a first data object of one of the second events is not a priority data object type;
- in response to determining that the type of the first data object of the one of the second events is not a priority data object type, updating, by the second service, a second one or more documents of the document database based on a second operation of the one of the second events, the updating including updating fields of the second one or more documents as specified in the operation associated with the second event;
- receiving the first events from the first event log and the second events from the second event log at a third service;
- determining, at the third service, that a type of a third data object of one of the first events is a priority data object type;
- in response to determining that a type of the third data object of the one of the first events is a priority data object type, updating, by the third service, a third one or more documents of the document database based on a third operation of the one of the first events, the updating including updating fields of the third one or more documents as specified in the operation associated with the first event;
- determining at the third service that a type of a fourth data object of one of the second events is a priority data object type;
- and
- in response to determining that the type of fourth data object of the one of the second events is a priority data object type, updating, by the third service, a fourth one or more documents of the document database based on a fourth data operation of the one of the second events, the updating including updating fields of the fourth one or more documents as specified in the operation associated with the second event.
9 more elements
One or more non-transitory computer-readable media storing program code that, when executed by a computing system, causes the computing system to perform operations comprising:
- receiving first events from a first event log, each first event associated with a data object and an operation on an instance of the data object;
- determining that a type of a first data object of one of the first events is not a priority data object type;
- in response to determining that the type of the first data object of the one of the first events is not a priority data object type, updating a first one or more documents of a document database based on a first operation of the one of the first events, the updating including fields of the first one or more documents as specified in the operation associated with the first event;
- receiving second events from a second event log, each second event associated with a data object and an operation on an instance of the data object;
- determining that a type of a first data object of one of the second events is not a priority data object type;
- in response to determining that the type of the first data object of the one of the second events is not a priority data object type, updating a second one or more documents of the document database based on a second operation of the one of the second events, the updating including updating fields of the second one or more documents as specified in the operation associated with the second event;
- determining that a type of a third data object of one of the first events is a priority data object type;
- in response to determining that a type of the third data object of the one of the first events is a priority data object type, updating a third one or more documents of the document database based on a third operation of the one of the first events, the updating including updating fields of the third one or more documents as specified in the operation associated with the first event;
- determining that a type of a fourth data object of one of the second events is a priority data object type;
- and
- in response to determining that the type of fourth data object of the one of the second events is a priority data object type, updating a fourth one or more documents of the document database based on a fourth data operation of the one of the second events, the updating including updating fields of the fourth one or more documents as specified in the operation associated with the second event.
8 more elements
Dependencies are inferred from the claim text.