Selective messaging for reducing server load
Implementations selectively message member account data to client applications to reduce server load. When a monitored load on cloud servers meets a criteria, a hold status may be triggered. During the hold status, member accounts may be monitored and client applications may be transmitted push messages, for example when a change is detected in a member's monitored account. The push messages can contain the detected changes, such as a posted transaction that triggered the message. Implementations of the client application can be configured to display local data (stored from the push messages) during the hold status in response to a member's request to access/view their account. Because server to client communication is limited to messages that contain member account changes, an overall server load can be reduced.
1. A method for reducing server load by pushing data to client applications, the method comprising:
transmitting, to a client application, a hold status for outbound requests, wherein the hold status comprises an expiration time;
monitoring changes to a user's account, wherein at least a portion of the changes are caused by account transactions; and
pushing, while the hold status is unexpired, one or more account updates to the client application based on defined update parameters, wherein:
the update parameters define a set of rules that filter which account updates are pushed to client devices based on one or more of: a) account balance; b) a predetermined period of time; c) a specified transaction entity; or d) a combination thereof;
the client application is configured to store the pushed account updates locally, and
the client application is configured to display user account data from the locally stored account updates in response to a user command.
2. The method of claim 1 , wherein the hold status transmittal is in response to a monitored load on one or more cloud systems, and wherein the monitored load on the one or more cloud systems comprises processor utilization for cloud server devices that process client application requests to access user accounts.
3. The method of claim 1 , wherein:
the client application pauses outbound requests for account data until the expiration time, and
after the expiration time, the client application is configured to resume outbound requests to the cloud systems for account data.
4. The method of claim 1 , further comprising:
detecting access patterns for the user's account; and
recommending update parameters for the user's account based on the detected access patterns.
5. The method of claim 4 , wherein the access patterns are detected by a machine learning model that analyzes historic log data representative of activity for the user's account.
6. The method of claim 1 ,
wherein the pushing, while the hold status is unexpired, the account updates to the client application is based on predictions generated by a machine learning model, wherein,
the machine learning model receives one or more account transactions as input and predicts a likelihood of user account access as output, and
one or more account updates are triggered when the predicted output generated by the machine learning model meets a confidence criteria.
7. The method of claim 6 , wherein the machine learning model is trained using historic log data representative of user account actions and historic transaction data for the user's account.
8. The method of claim 1 , wherein:
the update parameters define an active time period for account updates, and
when an account update is triggered outside the active time period, the account update is delayed by a period of time and the account update is transmitted at least by a start of the active time period.
9. The method of claim 8 , wherein the active time period is defined by a start time comprising a first time of day and an end time comprising a second time of day.
10. A computer-readable storage medium storing instructions that, when executed by a computing system, cause the computing system to perform a process to reduce server load by pushing data to client applications, the process comprising:
transmitting, to a client application, a hold status for outbound requests, wherein the hold status comprises an expiration time;
monitoring changes to a user's account, wherein at least a portion of the changes are caused by account transactions; and
pushing, while the hold status is unexpired, one or more account updates to the client application based on defined update parameters, wherein:
the update parameters define a set of rules that filter which account updates are pushed to client devices based on one or more of: a) account balance; b) a predetermined period of time; c) a specified transaction entity; or d) a combination thereof;
the client application is configured to store the pushed account updates locally, and
the client application is configured to display user account data from the locally stored account updates in response to a user command.
11. The computer-readable storage medium of claim 10 , wherein the hold status transmittal is in response to a monitored load on one or more cloud systems, and wherein the monitored load on the one or more cloud systems comprises processor utilization for cloud server devices that process client application requests to access user accounts.
12. The computer-readable storage medium of claim 10 , wherein:
the client application pauses outbound requests for account data until the expiration time, and
after the expiration time, the client application is configured to resume outbound requests to the cloud systems for account data.
13. The computer-readable storage medium of claim 10 , wherein the process further comprises:
detecting access patterns for the user's account; and
recommending update parameters for the user's account based on the detected access patterns.
14. The computer-readable storage medium of claim 13 , wherein the access patterns are detected by a machine learning model that analyzes historic log data representative of activity for the user's account.
15. The computer-readable storage medium of claim 10 ,
wherein the pushing, while the hold status is unexpired, the account updates to the client application is based on predictions generated by a machine learning model, wherein,
the machine learning model receives one or more account transactions as input and predicts a likelihood of user account access as output, and
one or more account updates are triggered when the predicted output generated by the machine learning model meets a confidence criteria.
16. The computer-readable storage medium of claim 15 , wherein the machine learning model is trained using historic log data representative of user account actions and historic transaction data for the user's account.
17. The computer-readable storage medium of claim 10 , wherein:
the update parameters define an active time period for account updates, and
when an account update is triggered outside the active time period, the account update is delayed by a period of time and the account update is transmitted at least by a start of the active time period.
18. The computer-readable storage medium of claim 17 , wherein the active time period is defined by a start time comprising a first time of day and an end time comprising a second time of day.
19. A computing system for reducing server load by pushing data to client applications, the system comprising:
one or more processors; and
one or more memories storing instructions that, when executed by the one or more processors, cause the computing system to perform a process comprising:
transmitting, to a client application, a hold status for outbound requests, wherein the hold status comprises an expiration time;
monitoring changes to a user's account, wherein at least a portion of the changes are caused by account transactions; and
pushing, while the hold status is unexpired, one or more account updates to the client application based on defined update parameters, wherein:
the update parameters define a set of rules that filter which account updates are pushed to client devices based on one or more of: a) account balance; b) a predetermined period of time; c) a specified transaction entity; or d) a combination thereof;
the client application is configured to store the pushed account updates locally, and
the client application is configured to display user account data from the locally stored account updates in response to a user command.
20. The system of claim 19 , wherein the hold status transmittal is in response to a monitored load on one or more cloud systems, and wherein the monitored load on the one or more cloud systems comprises processor utilization for cloud server devices that process client application requests to access user accounts.