Optimizing data synchronization between mobile clients and database systems

• US 8,832,061 B2
• Filed: 07/01/2011
• Issued: 09/09/2014
• Est. Priority Date: 07/02/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Kothule, Deepak, Mazyan, Bagrat, Forsberg, Erik, Zhulina, Aleksandra, Bergamo, Pierpaolo
• Primary Examiner(s): VU, BAI DUC
• Application Number:
  US13/175,728
• Publication Number:
  US 20120173485A1
• Time in Patent Office: 1,166 Days
• Field of Search: None
• US Class Current: 707/707
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing

Abstract

Mechanisms and methods are provided for optimizing data synchronization between clients and database systems. These mechanisms and methods provide optimizations for synchronization requests, by either breaking a synchronization request into multiple smaller requests, or by executing different code routines for differing client types, or by pre-caching data that a user is anticipated to want at a future point. Such optimization techniques can enable clients with varying capacities (e.g., mobile client vs. full desktop client) to optimally utilize their respective device capabilities.

Claims

1. A method of providing a response from a database system to a user of the database system, the method comprising:

receiving a request associated with a plurality of different types of data stored in the database;

dividing, with a server, the request into separate operations, wherein the dividing of the request is based on the different types of data;

obtaining separate partial results based on the breaking of the request into separate operations, wherein the separate partial results are obtained at a plurality of times, wherein at least one of the partial results is obtained in near real-time for a type of dataset that requires faster response times to be synced with the requesting client; and

sending each partial result to the user at the time the partial result is obtained.

2. The method of claim 1, wherein one of the types of data is news feed updates.

3. The method of claim 1, wherein the obtaining of separate partial results for the dataset that requires faster response times is performed by directly querying the database, bypassing any caching server.

4. The method of claim 1, wherein the obtaining of separate partial results for the dataset that requires faster response times is performed by retrieving said partial results from a caching system designed to maintain a cache for data requiring faster response times.

5. The method of claim 1, wherein the separate operations are performed in a pipeline.

6. The method of claim 1, wherein the partial result is sent to a mobile device of the user.

7. The method of claim 1, further comprising:

determining a priority among the separate operations, performing operations with a higher priority before operations with a lower priority.

8. The method of claim 1, wherein obtaining updates to feeds for users and records of the database is given a high priority.

9. The method of claim 1, wherein the feeds that are the most recently active are given a higher priority.

10. The method of claim 1, wherein a client device of the user merges the partial results.

11. The method of claim 1 wherein the dividing the request into separate operations comprises:

determining a first portion of the request is associated with a first different type of data; and

determining a second portion of the request is associated with a second different type of data, wherein data of the first different type changes more frequently than data of the second different type, the data of the first different type being the type of dataset that requires faster response times to be synced with the requesting client.

12. The method of claim 1 wherein the user is a first user, and a first partial result comprises a comment from a second user of the database system.

13. The method of claim 12 wherein the first user is following the second user.

14. The method of claim 1 wherein data of a first different type of data changes more frequently than data of a second different type of data.

15. A computer program product comprising a tangible non-transitory computer readable medium storing a plurality of instructions for controlling a processor to perform an operation for providing a response from a database system to a user of the database system, the instructions comprising:

receiving a request associated with a plurality of different types of data stored in the database;

dividing, with a server, the request into separate operations, wherein the dividing of the request is based on the different types of data;

obtaining separate partial results based on the breaking of the request into separate operations, wherein the separate partial results are obtained at a plurality of times, wherein at least one of the partial results is obtained in near real-time for a type of dataset that requires faster response times to be synced with the requesting client; and

sending each partial result to the user at the time the partial result is obtained.

16. The computer program product of claim 15 wherein the instructions comprise:

determining a first portion of the request is associated with a first different type of data; and

determining a second portion of the request is associated with a second different type of data, wherein data of the first different type changes more frequently than data of the second different type, the data of the first different type being the type of dataset that requires faster response times to be synced with the requesting client.

17. A method comprising:

receiving at a server a request for data from a user at a client;

determining that the request is associated with a first type of data, and a second type of data, different from the first type of data;

dividing the request into a first operation to retrieve data of the first type, and a second operation to retrieve data of the second type;

obtaining a first partial result from the first operation, the first partial result comprising the data of the first type;

sending the first partial result from the server to the client for the data of the first type to be presented at the client;

obtaining a second partial result from the second operation, the second partial result comprising the data of the second type; and

sending the second partial result from the server to the client for the data of the second type to be presented at the client, wherein the data of the first type has a higher priority than the data of the second type, and the data of the first type is presented at the client before the data of the second type is presented at the client.

18. The method of claim 17 comprising:

retrieving the data of the second type from a caching server; and

bypassing the caching server to retrieve the data of the first type from a database.

19. The method of claim 17 wherein the obtaining the second partial result comprises retrieving the data of the second type from a caching server, and the obtaining the first partial result comprises retrieving the data of the first type from a database and without accessing the caching server.

20. The method of claim 17 wherein the data of the first type has a higher priority than the data of the second type because the data of the first type changes more frequently than the data of the second type.

21. The method of claim 17 wherein the data of the first type has a higher priority than the data of the second type because a rate of change associated with the data of the first type is greater than a rate of change associated with the data of the second type.

22. The method of claim 17 wherein the user at the client is a first user, and the data of the first type comprises a comment from a second user.

23. The method of claim 22 wherein the first user is following the second user.

24. The method of claim 17 wherein the data of the first type comprises a status update to a record being followed by the user.