Systems and methods for real-time processing and transmitting of high-priority notifications
Systems and methods are disclosed for secure transmission of high-priority computer server event notifications. One method comprises obtaining a new computer server event to report; generating a first notification message pertaining to the computer server event; generating a second notification message pertaining to the computer server event and to the delivery of the first notification message; storing the first notification message; storing the second notification message; and transmitting the first notification message to a partner over a computer network.
1. A method for secure transmission of high-priority computer server event notifications, the method comprising:
generating a high-priority notification message based on one or more data components collected via a create event operation;
transmitting the high-priority notification message to a first queue client;
transmitting a delayed delivery message to a second queue client;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol, wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or
de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system, and transmitting the delayed delivery message to a downstream system.
2. The method of claim 1 , further comprising:
receiving server event information from a notification source; and
performing a create event operation based on the server event information.
3. The method of claim 1 , wherein the delayed delivery message indicates a notification error.
4. The method of claim 1 , wherein the high-priority notification message comprises at least one of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
5. The method of claim 4 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
6. The method of claim 1 , wherein the acknowledgement is received concurrently with a status update.
7. The method of claim 1 , wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details.
8. A system for secure transmission of high-priority computer server event notifications, the system comprising:
one or more processors; and
one or more computer readable media comprising instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
generating a high-priority notification message based on one or more data components collected via a create event operation;
transmitting the high-priority notification message to a first queue client; transmitting a delayed delivery message to a second queue client;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or
de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system, and transmitting the delayed delivery message to a downstream system.
9. The system of claim 8 , wherein the operations further comprise:
receiving server event information from a notification source; and
performing a create event operation based on the server event information.
10. The system of claim 8 , wherein the delayed delivery message indicates a notification error.
11. The system of claim 8 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
12. The system of claim 11 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
13. The system of claim 8 , wherein the acknowledgement is received concurrently with a status update.
14. The system of claim 8 , wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details.
15. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform operations for secure transmission of high-priority computer server event notifications, the operations comprising:
generating a high-priority notification message based on one or more data components collected via a create event operation;
transmitting the high-priority notification message to a first queue client;
transmitting a delayed delivery message to a second queue client;
denoting the high-priority notification message as sent based on determining that the acknowledgement is received from a partner system, wherein the high-priority notification message in the first queue client is configured to be transmitted to the partner system via a security protocol, wherein the security protocol is one of: message authentication code (MAC), JavaScript Object Notation Web Token (JWT), or Hypertext Transfer Protocol Secure (HTTPS); and
removing the delayed delivery message from the second queue client based on determining that the acknowledgement is received from the partner system; or
de-queuing the delayed delivery message based on determining that the acknowledgment is not received from the partner system, and transmitting the delayed delivery message to a downstream system.
16. The non-transitory computer-readable medium of claim 15 , wherein the operations further comprise:
receiving server event information from a notification source; and
performing a create event operation based on the server event information.
17. The non-transitory computer-readable medium of claim 15 , wherein the delayed delivery message indicates a notification error.
18. The non-transitory computer-readable medium of claim 15 , wherein the high-priority notification message comprises one or more of: an event type, case information, control information, device information, contact information, transaction information, or a variable list.
19. The non-transitory computer-readable medium of claim 18 , wherein the high-priority notification message further comprises information on whether there has been opt-out of reporting to a downstream system.
20. The non-transitory computer-readable medium of claim 15 , wherein the one or more data components collected via the create event operation comprise at least one of: a notification identifier (ID), a notification type, or notification details.