Event-driven cache
US-10467143-B1 · Nov 5, 2019 · US
US11016993B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11016993-B2 |
| Application number | US-201816201870-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 27, 2018 |
| Priority date | Nov 27, 2018 |
| Publication date | May 25, 2021 |
| Grant date | May 25, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
To reduce the amount of data traffic flowing between a remote computing platform and a client device, a manager for a data store of the client device is configured to observe upserts to the data store for one or more objects for a current connection session reflected therein; track fresh objects of a plurality of objects stored within the local data store, wherein fresh objects are identified as having an upsert during the current connection session; observe gets from the data store for one or more objects of the plurality of objects, and upon detecting a get for a particular object, determining whether the particular object is fresh, and if the object is detected to be stale, initiate an upsert from the remote computing platform to the data store for the particular object.
Opening claim text (preview).
That which is claimed: 1. A system comprising at least one processor and at least one non-transitory memory storing computer executable instructions that when executed by the processor cause the system to carry out actions, the processor programmed to: observe upserts to a client device data store in a client device for one or more objects of a plurality of objects, wherein the upserts are received from a remote computing platform; track fresh objects of the plurality of objects for a current connection session, wherein the fresh objects are identified as having an upsert during the current connection session; observe gets from the client device data store for one or more objects of the plurality of objects, wherein the gets relate to one or more local processing instances of the client device; upon detecting a get for a particular object of the plurality of objects: determine whether the particular object is a fresh object; and upon determining that that the particular object is not a fresh object, initiate an upsert from the remote computing platform to the client device data store for the particular object; and before initiating the upsert from the remote computing platform to the data store for the particular object, identify the particular object as a fresh object. 2. The system of claim 1 , wherein each of the plurality of objects have a corresponding object identifier, and wherein tracking fresh objects comprises: maintaining a session-specific indication of object identifiers corresponding with fresh objects for the current connection session. 3. The system of claim 2 , wherein the particular object has a corresponding particular object identifier; and wherein determining whether the particular object is a fresh object comprises: comparing the particular object identifier corresponding with the particular object against the session-specific indication of object identifiers corresponding with fresh objects for the current connection session. 4. The system of claim 1 , wherein tracking fresh objects comprises: tagging one or more objects of the plurality of objects with a connection session identifier indicative of a connection session during which a most recent upsert was received for a corresponding object of the one or more objects; and wherein fresh objects are tagged with a connection session identifier matching a current session identifier corresponding with the current connection session. 5. The system of claim 1 , wherein tracking fresh objects comprises updating a binary fresh/stale indicator associated with one or more objects to reflect a fresh state. 6. The system of claim 1 , further configured to: detect the initialization of a new connection session with the remote computing platform; and clear previously tracked fresh objects for a previous connection session. 7. The system of claim 4 , further configured to: detect the initialization of a new connection session with the remote computing platform; generate a new connection session identifier for the new connection session; and wherein, upon detecting a get for a particular object of the plurality of objects: determining whether the particular object is a fresh object comprises comparing a connection session identifier tagged with the particular object against the new connection session identifier for the new connection session. 8. The system of claim 1 , further configured to, upon detecting a get for a particular object of the plurality of objects: before determining whether the particular object is a fresh object, provide the object to the one or more local processing instances. 9. A method for managing a data store embodied within a memory storage area of a client device, the method comprising: observing upserts to the data store for one or more objects of a plurality of objects, wherein the upserts are received from a remote computing platform; tracking fresh objects of the plurality of objects for a current connection session, wherein the fresh objects are identified as having an upsert during the current connection session; observing gets from the data store for one or more objects of the plurality of objects, wherein the gets relate to one or more local processing instances of the client device; upon detecting a get for a particular object of the plurality of objects: determining whether the particular object is a fresh object; and upon determining that that the particular object is not a fresh object, initiating an upsert from the remote computing platform to the data store for to the particular object; and before initiating the upsert from the remote computing platform to the data store for the particular object, identify the particular object as a fresh object. 10. The method of claim 9 , wherein each of the plurality of objects have a corresponding object identifier, and wherein tracking fresh objects comprises: maintaining a session-specific listing of object identifiers corresponding with fresh objects for the current connection session. 11. The method of claim 10 , wherein the particular object has a corresponding particular object identifier; and wherein determining whether the particular object is a fresh object comprises: comparing the particular object identifier corresponding with the particular object against the session-specific listing of object identifiers corresponding with fresh objects for the current connection session. 12. The method of claim 9 , wherein tracking fresh objects comprises: tagging one or more objects of the plurality of objects with a connection session identifier indicative of a connection session during which a most recent upsert was received for a corresponding object of the one or more objects; and wherein fresh objects are tagged with a connection session identifier matching a current session identifier corresponding with the current connection session. 13. The method of claim 9 , wherein tracking fresh objects comprises wherein tracking fresh objects comprises updating a binary fresh/stale indicator associated with one or more objects to reflect a fresh state. 14. The method of claim 9 , further comprising: detecting the initialization of a new connection session with the remote computing platform; and clearing previously tracked fresh objects for a previous connection session. 15. The method of claim 14 , further comprising: detecting the initialization of a new connection session with the remote computing platform; generating a new connection session identifier for the new connection session; and wherein, upon detecting a get for a particular object of the plurality of objects: determining whether the particular object is a fresh object comprises comparing a connection session identifier tagged with the particular object against the new connection session identifier for the new connection session. 16. The method of claim 9 , further comprising, upon detecting a get for a particular object of the plurality of objects: before determining whether the particular object is a fresh object, providing the object to the one or more local processing instances. 17. A computer program product for managing a data store embodied within a memory storage area of a client device, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising an executable portion configured to: observe upserts to the data store for one or more objects of a plurality of o
Updates performed during online database operations; commit processing · CPC title
User profiles · CPC title
Databases characterised by their database models, e.g. relational or object models · CPC title
Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.