Processing mutations for a remote database

Patent metadata

Field	Value
Publication number	US-12174822-B2
Application number	US-202217821635-A
Country	US
Kind code	B2
Filing date	Aug 23, 2022
Priority date	Jun 24, 2014
Publication date	Dec 24, 2024
Grant date	Dec 24, 2024

Abstract

Methods, systems, and apparatus are described for processing mutations for a remote database. In one aspect, a method includes receiving a log of database mutations from a client device, the log of database mutations indicating changes previously made to a client version of a database stored on the client device, and each database mutation specifying: an entity included in the database; an operation for the entity; and a client version number for the entity; identifying, in the log of database mutations, two or more database mutations that each specify a same client version number for a same entity; determining, based on a conflict resolution policy, that the two or more database mutations are eligible for collapsing; and collapsing the two or more database mutations into a single database mutation.

First claim

What is claimed is:

1. A computer-implemented method executed by data processing apparatus of a remote version of a database that causes the data processing apparatus to perform operations comprising:
receiving, from a client device, a request requesting to update the remote version of the database with a client version of the database, the remote version of the database comprising a first value for an entity and the client version of the database comprising a second value for the entity that is greater than the first value for the entity, the remote version of the database remote from the client device and the client version of the database stored on the client device, wherein the request comprises:
a client database version number representing a version of the client version of the database; and
a client value to update a corresponding remote value of the remote version of the database;

determining, based on the client database version number of the request and a remote database version number representing the version of the remote version of the database, a conflict;
based on a conflict resolution policy specific to the database, determining that the second value for the entity is greater than the first value for the entity;
based on determining that the second value for the entity is greater than the first value for the entity, determining not to perform the request; and
providing, to the client device, conflict response data indicating that the request was not performed, the conflict response data configured to cause the client device to update the second value for the entity of the client version of the database with the first value for the entity, the conflict response data comprising:
the remote database version number; and
the first value for the entity of the remote version of the database.

2. The method of claim 1 , wherein the conflict resolution policy comprises a default resolution policy stored with the remote version of the database.

3. The method of claim 1 , wherein the conflict resolution policy further specifies to resolve the conflict in favor of the remote version of the database.

4. The method of claim 1 , wherein determining the conflict comprises determining that the client database version number is different than the remote database version number.

5. The method of claim 1 , wherein determining the conflict resolution policy comprises determining that the request does not specify a requested resolution policy.

6. The method of claim 1 , wherein the request comprises the conflict resolution policy.

7. The method of claim 1 , wherein the client database version number and the remote database version number comprise monotonically increasing values representing a number of updates to the database.

8. The method of claim 1 , wherein the database comprises a plurality of entities, each respective entity of the plurality of entities uniquely identified by a respective key.

9. The method of claim 8 , wherein the request comprises the respective key of an entity of the plurality of entities to update.

10. A system comprising:
data processing hardware of a remote version of a database; and
memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising:
receiving, from a client device, a request requesting to update the remote version of the database with a client version of the database, the remote version of the database comprising a first value for an entity and the client version of the database comprising a second value for the entity that is greater than the first value for the entity, the remote version of the database remote from the client device and the client version of the database stored on the client device, wherein the request comprises:
a client database version number representing a version of the client version of the database; and
a client value to update a corresponding remote value of the remote version of the database;

determining, based on the client database version number of the request and a remote database version number representing the version of the remote version of the database, a conflict;
based on a conflict resolution policy specific to the database determining that the second value for the entity is greater than the first value for the entity;
based on determining that the second value for the entity is greater than the first value for the entity, determining not to perform the request; and
providing, to the client device, conflict response data indicating that the request was not performed, the conflict response data configured to cause the client device to update the second value for the entity of the client version of the database with the first value for the entity, the conflict response data comprising:
the remote database version number; and
the corresponding remote value of the remote version of the database.

11. The system of claim 10 , wherein the conflict resolution policy comprises a default resolution policy stored with the remote version of the database.

12. The system of claim 10 , wherein the conflict resolution policy further specifies to resolve the conflict in favor of the remote version of the database.

13. The system of claim 10 , wherein determining the conflict comprises determining that the client database version number is different than the remote database version number.

14. The system of claim 10 , wherein determining the conflict resolution policy comprises determining that the request does not specify a requested resolution policy.

15. The system of claim 10 , wherein the request comprises the conflict resolution policy.

16. The system of claim 10 , wherein the client database version number and the remote database version number comprise monotonically increasing values representing a number of updates to the database.

17. The system of claim 10 , wherein the database comprises a plurality of entities, each respective entity of the plurality of entities uniquely identified by a respective key.

18. The system of claim 17 , wherein the request comprises the respective key of an entity of the plurality of entities to update.

Assignees

• Google Llc

Inventors

• Chen Jianjun
• Fuller Alfred R K
• Tsai Steve

Classifications

• G06F16/27

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/2474

  Sequence data queries, e.g. querying versioned data · CPC title

• G06F16/2358 Primary

  Change logging, detection, and notification (replication G06F16/27) · CPC title

• G06F16/2329

  using versioning · CPC title

• G06F16/2365 Primary

  Ensuring data consistency and integrity · CPC title