Persisted data cache service

A method implemented in a data processing system for caching data, the method comprising:

• initializing a single instance of a persisted cache service on the data processing system, the persisted cache service being a singleton, shared service and being registered with a service locator which is configured to receive requests for the persisted cache service and to return the single instance of the persisted cache service;
• receiving data requests from a plurality of single page applications (SPAs) on the data processing system;
• processing the data requests using a fetch command provided by an HTTP controller, the fetch command accessing the persisted cache service via the service locator and using the persisted cache service to obtain the requested data from a cache implemented on the data processing system or from one or more remote data sources via a network connection, wherein the cache is organized into a plurality of key-value pairs, each key-value pair representing a cache entry and including a cache key and a cache value, the cache key being calculated for the cache entry based on request parameters associated with a data request, and the cache value representing data obtained from the one or more remote data sources pertaining to the data request;
• providing the requested data obtained from the cache or the one or more remote data sources to an SPA of the plurality of SPAs from which each data request originated;
• serializing one or more request parameters associated with a data request to generate serialized request data;
• hashing the serialized request data to generate a first hashed value;
• obtaining user information associated with a user associated with the data request;
• serializing the user information to generate a second hashed value;
• appending the first hashed value to the second hashed value to generate the cache key associated with the data request;
• receiving an event notification of a user-related event that includes a Universal Resource Locator (URL) in a payload of the event notification, wherein the URL indicates a domain associated with the user-related event;
• identifying at least a portion of data in the cache associated with the URL;
• and
• invalidating the at least a portion of the data in the cache associated with the URL.

A non-transitory computer-readable storage medium on which are stored instructions that when executed cause a processor of a programmable device to perform functions of:

• initializing a single instance of a persisted cache service on the programmable device, the persisted cache service being a singleton, shared service and being registered with a service locator which is configured to receive requests for the persisted cache service and to return the single instance of the persisted cache service;
• receiving data requests from a plurality of single page applications (SPAs) on the programmable device;
• processing the data requests using a fetch command provided by an HTTP controller, the fetch command accessing the persisted cache service via the service locator and using the persisted cache service to obtain the requested data from a cache implemented on the programmable device or from one or more remote data sources via a network connection, wherein the cache is organized into a plurality of key-value pairs, each key-value pair representing a cache entry and including a cache key and a cache value, the cache key being calculated for the cache entry based on request parameters associated with a data request, and the cache value representing data obtained from the one or more remote data sources pertaining to the data request;
• and
• providing the requested data obtained from the cache or the one or more remote data sources to an SPA of the plurality of SPAs from which each data request originated.
• serializing one or more request parameters associated with a data request to generate serialized request data;
• hashing the serialized request data to generate a first hashed value;
• obtaining user information associated with a user associated with the data request;
• serializing the user information to generate a second hashed value;
• appending the first hashed value to the second hashed value to generate the cache key associated with the data request;
• receiving an event notification of a user-related event that includes a Universal Resource Locator (URL) in a payload of the event notification, wherein the URL indicates a domain associated with the user-related event;
• identifying at least a portion of data in the cache associated with the URL;
• and
• invalidating the at least a portion of the data in the cache associated with the URL.