Systems and methods for subscribing topics and registering computer server event notifications
Systems and methods are disclosed for secure transmission of computer server event notifications, including receiving a topic subscription request from a partner, registering the partner topic subscription request, obtaining a new computer server event to report, determining a subscribed partner subscribed to computer server events of a same type as the new computer server event, transmitting an event notification to the subscribed partner, and registering the event notification.
1. A computer-implemented method of processing server event subscription requests, the method comprising:
receiving, by a notification server, a server event subscription request from a partner system, the server event subscription request comprising an event type and being submitted to the notification server via a service gateway;
verifying, by the notification server, that the partner system is authorized to receive an event notification associated with the event type;
registering, by the notification server, the server event subscription request from the partner system in a database;
determining, by the notification server, an event in the database associated with the event type;
generating, by the notification server, a notification ID for the event associated with the event type;
querying, by the notification server, the database for one or more additional partner systems subscribed to the event and one or more additional events associated with the event type;
retrieving, by the notification server, the one or more additional events associated with the event type;
associating, by the notification server, the one or more additional events with the notification ID; and
transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems.
2. The computer-implemented method of claim 1 , further comprising:
requesting, by the notification server, a confirmation of receipt of the event notification from the partner system.
3. The computer-implemented method of claim 2 , further comprising:
upon receiving the confirmation of receipt from the partner system, marking, by the notification server, the event notification for the partner system in the database as sent.
4. The computer-implemented method of claim 2 , further comprising:
upon not receiving the confirmation of receipt from the partner system, incrementing, by the notification server, a counter of a number of attempts to deliver the event notification to the partner system; and
upon the number of attempts exceeding a predetermined threshold, marking, by the notification server, the event notification for the partner system in the database as permanently failed.
5. The computer-implemented method of claim 1 , further comprising:
prior to transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems, grouping, by the notification server, the event and the one or more additional events associated with the event type into the event notification upon determining that a predetermined number of events have been identified.
6. The computer-implemented method of claim 5 , wherein the predetermined number of events is configured for each event type of a plurality of event types and for each partner system of a plurality of partner systems.
7. The computer-implemented method of claim 5 , wherein the predetermined number of events is configured based on a time of day or a day of week.
8. The computer-implemented method of claim 1 , further comprising:
prior to transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems, determining, by the notification server, that a maximum number of events have been identified before a predetermined time period has passed,
wherein the event notification is transmitted to the partner system and the one or more additional partner systems upon receiving the maximum number of events before the predetermined time period has passed.
9. A system comprising:
one or more processors;
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 a method of processing server event subscription requests, the method comprising:
receiving, by a notification server, a server event subscription request from a partner system, the server event subscription request comprising an event type and being submitted to the notification server via a service gateway;
verifying, by the notification server, that the partner system is authorized to receive an event notification associated with the event type;
registering, by the notification server, the server event subscription request from the partner system in a database;
determining, by the notification server, an event in the database associated with the event type;
generating, by the notification server, a notification ID for the event associated with the event type;
querying, by the notification server, the database for one or more additional partner systems subscribed to the event and one or more additional events associated with the event type;
retrieving, by the notification server, the one or more additional events associated with the event type;
associating, by the notification server, the one or more additional events with the notification ID; and
transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems.
10. The system of claim 9 , the method further comprising:
requesting, by the notification server, a confirmation of receipt of the event notification from the partner system.
11. The system of claim 10 , the method further comprising:
upon receiving the confirmation of receipt from the partner system, marking, by the notification server, the event notification for the partner system in the database as sent.
12. The system of claim 10 , the method further comprising:
upon not receiving the confirmation of receipt from the partner system, incrementing, by the notification server, a counter of a number of attempts to deliver the event notification to the partner system; and
upon the number of attempts exceeding a predetermined threshold, marking, by the notification server, the event notification for the partner system in the database as permanently failed.
13. The system of claim 9 , the method further comprising:
prior to transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems,
grouping, by the notification server, the event and the one or more additional events associated with the event type into the event notification upon determining that a predetermined number of events have been identified.
14. The system of claim 13 , wherein the predetermined number of events is configured for each event type of a plurality of event types and for each partner system of a plurality of partner systems.
15. The system of claim 13 , wherein the predetermined number of events is configured based on a time of day or a day of week.
16. The system of claim 9 , the method further comprising:
prior to transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems,
determining, by the notification server, that a maximum number of events have been identified before a predetermined time period has passed,
wherein the event notification is transmitted to the partner system and the one or more additional partner systems upon receiving the maximum number of events before the predetermined time period has passed.
17. One or more non-transitory computer readable media comprising instructions which, when executed by one or more processors, cause the one or more processors to perform a method of processing server event subscription requests, the method comprising:
receiving, by a notification server, a server event subscription request from a partner system, the server event subscription request comprising an event type and being submitted to the notification server via a service gateway;
verifying, by the notification server, that the partner system is authorized to receive an event notification associated with the event type;
registering, by the notification server, the server event subscription request from the partner system in a database;
determining, by the notification server, an event in the database associated with the event type;
generating, by the notification server, a notification ID for the event associated with the event type;
querying, by the notification server, the database for one or more additional partner systems subscribed to the event and one or more additional events associated with the event type;
retrieving, by the notification server, the one or more additional events associated with the event type;
associating, by the notification server, the one or more additional events with the notification ID; and
transmitting, by the notification server, the event notification to the partner system and the one or more additional partner systems.
18. The one or more non-transitory computer readable media of claim 17 , the method further comprising:
requesting, by the notification server, a confirmation of receipt of the event notification from the partner system.
19. The one or more non-transitory computer readable media of claim 18 , the method further comprising:
upon receiving the confirmation of receipt from the partner system, marking, by the notification server, the event notification for the partner system in the database as sent.
20. The one or more non-transitory computer readable media of claim 18 , the method further comprising:
upon not receiving the confirmation of receipt from the partner system, incrementing, by the notification server, a counter of a number of attempts to deliver the event notification to the partner system; and
upon the number of attempts exceeding a predetermined threshold, marking, by the notification server, the event notification for the partner system in the database as permanently failed.