Eventing systems and methods to facilitate robust event processing

#The present disclosure generally relates to facilitating event processing and, more particularly, to eventing systems and methods configured to increase processing throughput of new events retrieved via an application programming interface (API) by utilizing an event processing model.

#Generally speaking, eventing systems allow clients to receive updates, alerts, and other relevant notifications related to their areas of interest. For example, mobile application (app) eventing systems allow clients to receive notifications related to the client's mobile apps, such as software updates, directly to the client's mobile device. However, traditional mobile app eventing systems have suffered from a variety of issues.

#Broadly stated, traditional systems lack the ability to reliably process events. Traditional mobile app eventing systems are unable to effectively handle events that are received but not processed or stored before a mobile app is closed, events that are stored but are not properly processed, and removing events after they have been processed. Moreover, traditional systems fail to adequately prevent resource exhaustion when existing clients sign into new devices, do not actively adapt to be compatible with new events, and consistently disrupt event processing to existing clients when incorporating new clients.

#FIG. 1 illustrates an eventing system for facilitating event processing according to some embodiments;

#FIG. 2 illustrates another eventing system for facilitating event processing according to some embodiments;

#FIG. 3 depicts an operational embodiment of the eventing system of FIG. 2 according to some embodiments;

#The figures depict various aspects of the present disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.

#FIG. 1 illustrates an example eventing system 100 for facilitating event processing. The example system 100 may include a user device 102, an event server 104, external databases 106, and a network 108. While illustrated in FIG. 1 as a single external database, in some embodiments the external databases 106 includes two or more external databases. The network 108 may be a computer network of an insurance provider (e.g., provided or used by the insurance provider or communications over which the insurance provider otherwise controls or facilitates). The user device 102, and each of the computing devices referred to herein, may be any suitable computing device such as, but not limited to, a desktop computer, a laptop computer, a mobile phone such as a smart phone, a tablet, a phablet, smart glasses, other wearable computing device(s), etc.

#FIG. 2 illustrates another eventing system for facilitating event processing according to some embodiments. In reference to the example eventing system 200 of FIG. 2, the user device 102 may include a processor 202, a memory 204, a transceiver 206, and a display 208. While referred to herein as a “processor” and a “memory,” in some embodiments the processor 202 includes two or more processors and the memory 204 includes two or more memories. The memory 204 may include an event processing model 210 and an API protocol database 212, and may store computer-executable instructions, which may be executed by the processor 202.