Intermediate widget cache

A system, comprising:

• one or more processors;
• and
• a memory coupled to the one or more processors, wherein the memory is configured to provide the one or more processors with instructions which when executed cause the one or more processors to:
• determine a first expected usage start time associated with a first user;
• preload a first data for a first modular contained widget component of an application user interface into an identified cache instance based on the first expected usage start time associated with the first user including by evicting a second data associated with a second modular contained widget component associated with a second user having a second expected usage start time different from the first expected usage start time associated with the first user;
• receive from a client, a request for the first data to render the first modular contained widget component of the application user interface;
• determine at an intermediary server, whether the first data is cached at the intermediary server, wherein the first data is based at least in part on one or more database records stored at a backend server;
• in response to a determination that the first data is cached, obtain the first data from the identified cache instance that cached the first data, wherein the cached first data is based at least in part on the one or more database records provided by the backend server to the intermediary server to maintain an updated version of the first data at the identified cache instance;
• and
• provide to the client the first data from the intermediary server.

A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

• determining a first expected usage start time associated with a first user;
• preloading a first data for a first modular contained widget component of an application user interface into an identified cache instance based on the first expected usage start time associated with the first user including by evicting a second data associated with a second modular contained widget component associated with a second user having a second expected usage start time different from the first expected usage start time associated with the first user;
• receiving from a client, a request for the first data to render the first modular contained widget component of the application user interface;
• determining at an intermediary server, whether the first data is cached at the intermediary server, wherein the first data is based at least in part on one or more database records stored at a backend server;
• in response to a determination that the first data is cached, obtaining the first data from the identified cache instance that cached the first data, wherein the cached first data is based at least in part on the one or more database records provided by the backend server to the intermediary server to maintain an updated version of the first data at the identified cache instance;
• and
• providing to the client the first data from the intermediary server.