Technologies for configurable caching, deduplication, and rate limit handling

A method for configurable caching, deduplication, and rate limit handling of user interface data requests, the method comprising:

• receiving a data request initiated by a user interface element of a user interface;
• determining whether a deduplication cache includes a deduplication entry associated with the data request;
• determining whether a main cache, different from the deduplication cache, includes a cache entry associated with the data request in response to determining that the deduplication cache does not include the deduplication entry;
• and
• making the data request to a backend system after (i) determining that the main cache does not include the cache entry associated with the data request or (ii) determining that the cache entry associated with the data request has expired, the method further comprising:
• receiving an error associated with the data request in response to a failure to fulfill the data request;
• determining whether the error associated with the data request is a retriable error;
• determining whether a predefined retry limit has been reached in response to determining that the error associated with the data request is the retriable error;
• and
• retrying the data request in response to determining that the predefined retry limit has not been reached.

A system for configurable caching, deduplication, and rate limit handling of user interface data requests, the system comprising:

• a deduplication cache;
• a main cache different from the deduplication cache;
• at least one processor;
• and
• at least one memory comprising a plurality of instructions stored thereon that, in response to execution by the at least one processor, causes the system to:
• receive a data request initiated by a user interface element of a user interface;
• determine whether the deduplication cache includes a deduplication entry associated with the data request;
• determine whether the main cache includes a cache entry associated with the data request in response to a determination that the deduplication cache does not include the deduplication entry;
• and
• make the data request to a backend system after a determination that one of (i) the main cache does not include the cache entry associated with the data request or (ii) the cache entry associated with the data request has expired;
• wherein the main cache is configured to store resultant data returned from the backend system in response to one or more previous data requests;
• and
• the deduplication cache is configured to store one or more promises indicative of the one or more previous data requests and different from the resultant data.