Prepopulation of caches

1. A computer-implemented method comprising:

detecting, in a data stream, first information associated with a user;

storing, based on the detecting, the first information in an application cache associated with an application;

receiving, by a server and from the application, the first information from the application cache;

prepopulating a first action cache with at least some of the first information received from the application cache;

receiving a first request, by the server and from the application, a first request comprising a request for performing a first action associated with the user;

performing the first action;

prepopulating, with second information and based on the performance of the first action, a second action cache with at least some of the first information from the first action cache, wherein the second action cache is associated with detecting fraudulent transactions;

receiving, by the server and from the application, a second request comprising a request for performing a second action, wherein the second action comprises a transaction associated with a user account associated with the user;

determining, by the server and based on the second information in the prepopulated second cache, whether the second request, for performing the second action, is fraudulent; and

based on a determination that the second request is not fraudulent, performing the second action.

2. The computer-implemented method of claim 1 , further comprising:

storing the first information in the first action cache, wherein the first action assigns a time-to-live value to the first information; and

deleting, at an expiration of the time-to-live value of the first information, the first information from the first action cache.

3. The computer-implemented method of claim 1 , further comprising:

determining, based on receiving the first request from the application, whether to perform the first action,

wherein performing the first action is based on a determination to perform the first action.

4. The computer-implemented method of claim 1 , further comprising:

receiving, by the server and from the application, a third request comprising a request for performing the first action;

determining, by the server and based on the first information in the prepopulated first action cache, whether to perform the third request's first action; and

based on a determination to not perform the third request's first action, denying the third request.

5. The computer-implemented method of claim 1 ,

wherein the first action comprises opening a new account, and

wherein the first action cache comprises a cache of information from which a determination of whether the first request for the first action is fraudulent.

6. The computer-implemented method of claim 1 ,

wherein the first information associated with the user comprises a change to application information in the application cache,

wherein storing the first information comprises overwriting, in the application cache, existing user-specific information and refreshing a time-to-live value associated with the user-specific information in the application cache,

the method further comprising:

receiving, from the application, a third request for the user-specific information associated with the user; and

sending, to the application, the user-specific information.

7. The computer-implemented method of claim 6 , further comprising:

detecting second user-specific information in the data stream associated with the user, wherein the second user-specific information comprises information not currently stored in the application cache; and

storing, based on the detecting the second user-specific information, the second user-specific information in the application cache, wherein the second user-specific information receives a second time-to-live value,

wherein the receiving the third request for the user-specific information comprises receiving a request for the user-specific information and the second user-specific information, and

wherein sending the user-specific information comprises sending, to the application, the user-specific information and the second user-specific information.

8. The computer-implemented method of claim 7 , further comprising:

receiving, from the application, a fourth request for third user-specific information associated with the user;

determining the application cache does not currently store the third user-specific information;

receiving, from the server, the third user-specific information and a third time-to-live value;

storing, in the application cache, the third user-specific information and the third time-to-live value; and

sending, to the application, the third user-specific information.

9. An apparatus comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the apparatus to:

detect, in a data stream, first information associated with a user;

store, based on a detection of the first information, the first information in an application cache, associated with an application, with user-specific information;

receive, by a server and from the application, the first information from the application cache, wherein the first information comprises at least some of the user-specific information;

prepopulate a first action cache with at least some of the first information received from the application cache;

receive a first request, by the server and from the application, a first request comprising a request for performing a first action associated with the user;

perform the first action;

prepopulate, with second information and based on the performance of the first action, a second action cache with at least some of the first information from the first action cache, wherein the second action cache is associated with detecting fraudulent transactions;

receive, by the server and from the application, a second request comprising a request for performing a second action, wherein the second action comprises a transaction associated with a user account associated with the user;

determine, by the server and based on the second information in the prepopulated second cache, whether the second request, for performing the second action, is fraudulent; and

based on a determination that the second request is not fraudulent, perform the second action.

10. The apparatus of claim 9 , wherein the instructions further cause the apparatus to:

store the first information in the first action cache, wherein the first action assigns a time-to-live value to the first information; and

delete, at an expiration of the time-to-live value of the first information, the first information from the first action cache.

11. The apparatus of claim 9 , wherein the instructions further cause the apparatus to:

determine, based on receiving the first request from the application, whether to perform the first action,

wherein performance of the first action is based on a determination to perform the first action.

12. The apparatus of claim 9 , wherein the instructions further cause the apparatus to:

receive, by the server and from the application, a third request comprising a request for performing the first action;

determine, by the server and based on the first information in the prepopulated first action cache, whether to perform the third request's first action; and

based on a determination to not perform the third request's first action, denying the third request.

13. The apparatus of claim 9 ,

wherein the first action comprises opening a new account, and

wherein the first action cache comprises a cache of information from which a determination of whether the first request for the first action is fraudulent.

14. The apparatus of claim 9 ,

wherein the first information associated with the user comprises a change to user-specific information in the application cache,

wherein the instructions to store the first information comprises instructions to overwrite existing user-specific information and refresh a time-to-live value associated with the user-specific information in the application cache, and

wherein the instructions further cause the one or more processors to:

receive, from the application, a request for the user-specific information associated with the user; and

send, to the application, the user-specific information.

15. The apparatus of claim 14 , wherein the instructions further cause the apparatus to:

detect second user-specific information in the data stream associated with the user, wherein the second user-specific information comprises information not currently stored in the application cache; and

store, based on the detecting the second user-specific information, the second user-specific information in the application cache, wherein the second user-specific information receives a second time-to-live value,

wherein the receiving the third request for the user-specific information comprises receiving a request for the user-specific information and the second user-specific information, and

wherein sending the user-specific information comprises sending, to the application, the user-specific information and the second user-specific information.

16. The apparatus of claim 15 , wherein the instructions further cause the apparatus to:

receive, from the application, a fourth request for third user-specific information associated with the user;

determine the application cache does not currently store the third user-specific information;

receive, from the server, the third user-specific information and a third time-to-live value;

store, in the application cache, the third user-specific information and the third time-to-live value; and

send, to the application, the third user-specific information.

17. The apparatus of claim 16 ,

wherein the time-to-live value, the second time-to-live value, and the time-to-live value are different from each other.

18. One or more non-transitory media storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising:

detecting, in a data stream, first information associated with a user;

storing, based on the detecting, the first information in an application cache associated with an application;

receiving, by a server and from the application, the first information from the application cache;

prepopulating a first action cache with at least some of the first information received from the application cache;

receiving a first request, by the server and from the application, a first request comprising a request for performing a first action associated with the user;

determining, based on receiving the first request from the application, whether to perform the first action;

based on a determination to perform the first action, performing the first action;

prepopulating, with second information and based on the performance of the first action, a second action cache with at least some of the first information from the first action cache, wherein the second action cache is associated with detecting fraudulent transactions;

receiving, by the server and from the application, a second request comprising a request for performing a second action, wherein the second action comprises a transaction associated with a user account associated with the user;

determining, by the server and based on the second information in the prepopulated second cache, whether the second request, for performing the second action, is fraudulent; and

based on a determination that the second request is not fraudulent, performing the second action.