LOCAL CACHING AND RESOLUTION OF SERVICE CALLS

• US 20160080519A1
• Filed: 01/02/2015
• Published: 03/17/2016
• Est. Priority Date: 09/11/2014
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hansen, Marc, Robyns, Gert Willem, Chereches, Cristian, Hejlsberg, Thomas, Millard, Adam
• Application Number:
  US14/588,596
• Publication Number:
  US 20160080519A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

A local service system receives a call from a local application. The local service system determines whether an acceptable result to return for the call is already stored in a local service cache. If not, the local service system calls a remote service system to obtain a result, it returns the result to the local application, and stores the result in the local service cache.

Claims

1. A local service computing system that is local to a multi-user computing system and that responds to service calls from users of the multi-user computing system, comprising:

a local service cache that stores results from calls by the multi-user computing system to a remote service system;

a response engine that receives an incoming service call from the multi-user computing system to a remote service system and accesses the local service cache to determine whether the local service cache has an acceptable result that is responsive to the incoming service call and, if so, retrieves the acceptable result and responds to the incoming service call with the acceptable result; and

a remote service accessing engine that passes the incoming service call to the remote service system to receive a fresh result, in response to the response engine determining that the local service cache does not have an adequate result, the response engine responding to the incoming service call with the fresh result.

2. The local service computing system of claim 1 wherein the response engine determines whether the local service cache has an acceptable result by determining whether the local service cache has a responsive result that is responsive to the incoming service call and further comprises:

a cache refresh component that accesses a set of refresh rules and determines, based on the refresh rules and a freshness indicator on the responsive result, whether the responsive result is sufficiently fresh or needs to be refreshed from the remote service system.

3. The local service computing system of claim 2 wherein the incoming service call includes a freshness parameter and wherein the response engine further comprises:

a freshness parameter processing component that receives the freshness parameter and determines a corresponding freshness indicated by the freshness parameter, the cache refresh component determines whether the responsive result is sufficiently fresh based on the freshness determined by the freshness parameter processing component.

4. The local service computing system of claim 2 wherein the remote service accessing system calls the remote service system to receive over-inclusive results for a given incoming service call and receives the over-inclusive results from the remote service system, and further comprising:

a filtering component that parses the over-inclusive results to identify responsive results, the cache refresh component storing the over-inclusive results in the local service cache and identifying the responsive results as responsive to the given incoming service call in the local service cache.

5. The local service computing system of claim 2 and further comprising:

a request throttling component that determines when the multi-user computing system has reached a threshold call level to the remote service system and reduces the call level until the call level is within the threshold call level.

6. The local service computing system of claim 5 wherein the request throttling component reduces the call level by serializing service calls or multiplexing the service calls.

7. The local service computing system of claim 2 and further comprising:

a tracking component that logs characteristics of service calls made by the multi-user computing system for results from the remote service system; and

a refresh system that determines that a refresh operation is to be performed, identifies a set of results in the local service cache that are to be updated, based on the logged characteristics of the service calls, and refreshes the identified set of results with corresponding results from the remote service system.

8. The local service computing system of claim 7 wherein the refresh system refreshes the identified set of results by replaying service calls, that were used to obtain the identified set of results, against the remote service system.

9. The local service computing system of claim 8 wherein the refresh system identifies the set of results as those that are most frequently made by the multi-user computing system or those that take a greatest amount of processing overhead of the remote service system.

10. The local service computing system of claim 2 and further comprising:

a test result generation component that receives inputs indicative of test results to return to a calling application under test and that stores the test results in the local service cache, the response engine returning the test results when the application under test makes calls to the local service system; and

a test generation component that receives test inputs indicating that the application under test is to be tested and providing an output to the response engine indicating that, in response to calls from the application under test, the test results are to be returned.

11. The local service computing system of claim 2 and further comprising:

an authentication component that authenticates users of the multi-user computing system, the remote service accessing engine and the response engine responding to the authenticated users, without authentication of the users of the multi-user computing system to the remote service system.

12. A computer-implemented method, comprising:

receiving, at a local service system that is local to a multi-user computing system, a call from a calling system to a remote service system;

determining whether a matching result, that matches the call, is stored in a local service cache;

if so, accessing a set of refresh rules to determine whether the matching result is to be refreshed and, if the matching result is not to be refreshed, then returning the matching result to the calling system from the local service cache in response to the call; and

if the matching result is to be refreshed based on the refresh rules or if a matching result is not stored in the local service cache, then sending the call to the remote service system, receiving fresh results from the remote service system, and storing the fresh results in the local service cache.

13. The computer-implemented method of claim 12 and further comprising:

identifying characteristics of the call and storing the identified characteristics of the call.

14. The computer-implemented method of claim 13 and further comprising:

determining that a cache refresh is to be performed;

identifying cache results to be refreshed in the local service cache based on the stored characteristics of the call that requested the results; and

refreshing the identified cache results in the local service cache.

15. The computer-implemented method of claim 14 wherein identifying cache results to be refreshed comprises:

identifying all results in the local service cache as cache results to be refreshed.

17. The computer-implemented method of claim 14 wherein identifying cache results to be refreshed comprises:

identifying cache results responsive to a set of most frequent calls as the cache results to be refreshed.

18. The computer-implemented method of claim 14 wherein identifying cache results to be refreshed comprises:

identifying cache results as the cache results to be refreshed based on a computing overhead used by the remote service system in servicing corresponding calls for the cache results.

19. A computer readable storage medium that stores computer executable instructions which, when executed by a computer, cause the computer to perform a method, comprising:

receiving, at a local service system that is local to a multi-tenant computing system, a call from a calling system to a remote service system;

determining whether a matching result, that matches the call, is stored in a local service cache;

if so, accessing a set of refresh rules and a freshness parameter provided in the call to determine whether the matching result is to be refreshed and, if the matching result is not to be refreshed, then returning the matching result to the calling system from the local service cache in response to the call; and

if the matching result is to be refreshed based on the refresh rules or freshness parameter or if a matching result is not stored in the local service cache, then sending the call to the remote service system, receiving fresh results from the remote service system, and storing the fresh results in the local service cache.

20. The computer readable storage medium of claim 19 wherein the fresh result is over-inclusive of results responsive to the call, and further comprising:

parsing the fresh result to identify the results responsive to the call;

breaking the results responsive to the call into pages;

returning to the calling system the results responsive to the call; and

storing the results responsive to the call in the local service cache with a call indicator identifying the call the results are responsive to.