Consistent views of partitioned data in eventually consistent systems

• US 10,318,618 B2
• Filed: 06/18/2014
• Issued: 06/11/2019
• Est. Priority Date: 06/18/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Sevilmis, Tarkan, Kapadia, Arshish, Outcalt, Peter Adam
• Primary Examiner(s): Nabi, Reza
• Application Number:
  US14/308,429
• Publication Number:
  US 20150370767A1
• Time in Patent Office: 1,819 Days
• Field of Search: 715763
• CPC Class Codes: G06F 16/24552 Database cache management
• 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/93 Document management systems
• CPC Class Codes: G06F 40/166 Editing, e.g. inserting or deleting

Abstract

A consistent user view system. The system incorporates any changes made by a user in any views shown to that user even when the changes have not propagated to the partitions supplying the view. The system separates the authority for edits from the replicated storage allowing efficient transactions and linear scalability. Documents are read from view-based partitions of a store. Document writes are written to a document-specific partition in a journal and applied to the store. The system stores a copy of pending changes in a user-specific partition. When a user requests a view, the system checks that user'"'"'s cache for any pending changes applicable to the view. If any applicable changes are found, the changes are applied before showing the view to the user. Pending changes that have been successfully applied to the store are trimmed from the user-specific partition to free up resources.

Claims

1. A method, comprising:

receiving a read request submitted by a user, the read request associated with a source document stored in a storage unit;

retrieving, responsive to the read request, the source document from the storage unit;

retrieving a user view record responsive to the read request from a user-specific partition of a cloud storage resource, wherein the user view record is associated with the user and represents a pending write request to the source document;

generating an updated responsive view of the source document by merging the pending write request associated with the user view record with the source document;

causing presentation of the updated responsive view of the source document;

subsequent to causing the presentation of the updated responsive view, merging the pending write request with the source document stored in the storage unit to produce an updated source document; and

in response to producing the updated source document, deleting the user view record associated with the write request from the user-specific partition of the cloud storage resource.

2. The method of claim 1, further comprising providing an acknowledgement acknowledging receipt of the write request after the write request has been stored in the user-specific partition, the write request comprising one or more edits to the source document.

3. The method of claim 1, wherein:

the read request comprises a first read request;

the user-specific partition of the cloud storage resource comprises a first user-specific partition of the cloud storage resource;

the pending write request comprises a first pending write request;

the user comprises a first user;

the user view record comprises a first user view record; and

the method further comprises;

receiving a second read request submitted by a second user, wherein the second read request is associated with the source document;

responsive to the second read request and based on a determination that a second user-specific partition in the cloud storage resource associated with the second user does not store a second user view record that represents a second pending write request to the source document submitted by the second user, causing presentation of a responsive user view of the source document that is associated with the second user.

4. The method of claim 1, wherein:

the read request comprises a first read request;

the user-specific partition of the cloud storage resource comprises a first user-specific partition of the cloud storage resource;

the user comprises a first user;

the user view record comprises a first user view record;

the updated responsive view of the source document comprises a first updated responsive view of the source document; and

the method further comprises;

receiving a second read request submitted by a second user, wherein the second read request is associated with source document;

responsive to the second read request and while the write request associated with the first user is pending, storing a second user view record in a second user-specific partition of the cloud storage resource associated with the second user, wherein the second user view record is associated with the second user and represents the pending write request to the source document;

generating a second updated responsive view of the source document by merging the pending write request associated with the second user view record with the source document; and

causing presentation of the second updated responsive view of the source document.

5. The method of claim 1, further comprising:

receiving a query directed to the user-specific partition for an edit applicable to the source document from a client device caching the source document; and

sending the edit to the client device so the client device may update the cached source document with the edit to the source document.

6. The method of claim 1, wherein:

the storage unit comprises a first storage unit; and

the method further comprises;

receiving the write request submitted by the user, the write request comprising one or more user edits to the source document; and

storing a run record associated with the write request in a second storage unit.

7. A system comprising:

a first storage system storing and servicing write requests;

a second storage system storing documents and servicing read requests;

a user-specific partition of a cache associated with a user; and

a computing device having a processor and a memory, the computing device operable to;

store, in the first storage system, a write request submitted by the user and comprising an edit to a document stored in the second storage system;

store a user view record associated with the write request in the user-specific partition of the cache;

receive a read request submitted by the user, wherein the read request is associated with the document;

retrieve, responsive to the read request, the document from the second storage system;

retrieve the user view record responsive to the read request from the user-specific partition of the cache;

generate an updated responsive view of the document by merging the write request associated with the user view record with the document;

cause presentation of the updated responsive view of the document;

subsequent to causing the presentation of the updated responsive view, merge the write request with the document stored in the second storage system to produce an updated document; and

in response to producing the updated document, delete the user view record from the user-specific partition of the cache.

8. The system of claim 7, wherein the computing device is further operable to acknowledge receipt of the write request after storing the user view record in the user-specific partition of the cache.

9. The system of claim 7, wherein the computing device is further operable to provide only the document in responses to read requests submitted by other users.

10. The system of claim 7, wherein the computing device is further operable to assign a first version number to the write request stored in the first storage system that is different from a second version number of the document.

11. The system of claim 10, wherein the computing device is further operable to use the first version number as the version number of the document when responding to the read request from the user.

12. The system of claim 7, wherein:

the read request comprises a first read request;

the user-specific partition of the cache comprises a first user-specific partition of the cache;

the user view record comprises a first user view record;

the user comprises a first user; and

wherein the computing device is operable to;

receive, from a second user, a second read request associated with the document; and

store a second user view record associated with the write request in a second user-specific partition of the cache associated with the second user.

13. The system of claim 12, wherein:

the updated responsive view of the document comprises a first updated responsive view of the document; and

the computing device is operable to;

generate a second updated responsive view of the document by merging the write request associated with the second user view record with the document; and

cause presentation of the second updated responsive view of the document.

14. A method, comprising:

receiving a first read request submitted by a first user, the first read request associated with a document;

retrieving, responsive to the first read request, the document from a storage system;

retrieving a first user view record responsive to the first read request from a first user-specific partition of a cache, wherein the first user view record is associated with the first user and represents a first pending write request to the document submitted by the first user;

generating an updated responsive view of the document by merging the first pending write request associated with the first user view record with the document;

causing presentation of the updated responsive view of the document;

subsequent to causing the presentation of the updated responsive view, merging the first pending write request with the document stored in the storage system to produce an updated document;

prior to merging the first pending write request with the document, receiving a second read request submitted by a second user, the second read request associated with the document; and

responsive to the second read request and based on a determination that a second user-specific partition in the cache does not store a second user view record that represents a second pending write request to the document submitted by the second user, causing presentation of a responsive user view of the document that is associated with the second user.

15. The method of claim 14, further comprising in response to producing the updated document, deleting the first user view record from the first user-specific partition of the cache.

16. The method of claim 14, wherein:

the updated responsive view of the source document comprises a first updated responsive view of the document; and

the method further comprises;

prior to merging the first pending write request with the document, receiving a third read request submitted by a third user, wherein the third read request is associated with document;

responsive to the third read request, storing a third user view record in a third user-specific partition of the cache associated with the third user, wherein the third user view record is associated with the third user and represents the pending first write request to the document;

generating a second updated responsive view of the document by merging the pending first write request associated with the third user view record with the document; and

causing presentation of the second updated responsive view of the document.

17. The method of claim 14, further comprising providing an acknowledgement acknowledging receipt of the first write request after the first write request is stored in the first user-specific partition of the cache.

18. The method of claim 14, wherein:

the storage system comprises a first storage system; and

the method further comprises;

receiving the first write request submitted by the first user, the first write request comprising one or more edits to the document; and

storing a run record associated with the first write request in a second storage system.