EVENT FANNING PLATFORM FOR STREAMING NETWORK EVENT DATA TO CONSUMER APPLICATIONS
This disclosure describes an event fanning system that, as part of an inter-network facilitation system, can generate and provide consumer application data streams using an event fanning platform. For example, the disclosed systems can utilize an event fanning platform to generate application-specific data streams for providing requested network events. The disclosed systems can further tie a consumer application data stream to a lifecycle of the consumer application requesting one or more network events included within the data stream. Additionally, the disclosed systems can utilize the event fanning platform to generate updated consumer application data streams based on modifications to consumer applications.
1 . A method comprising:
receiving, from a consumer application, an event request indicating a requested network event from among a plurality of network events hosted by a network event data streaming platform;
generating, using an event fanning platform in response to the event request, a consumer application data stream specific to the requested network event and tied to a lifecycle of the consumer application;
providing, using the event fanning platform, the requested network event to the consumer application via the consumer application data stream; and
in response to detecting a deprecation of the consumer application, deprecating the consumer application data stream within the event fanning platform.
2 . The method of claim 1 , further comprising receiving the event request indicating the requested network event by:
receiving an application configuration file defining the consumer application; and
detecting, within the application configuration file, a code segment defining the requested network event.
3 . The method of claim 1 , further comprising generating the consumer application data stream by using the event fanning platform to generate a data stream configuration file defining the consumer application data stream to include the requested network event.
4 . The method of claim 1 , further comprising:
receiving, from an additional consumer application, an additional event request indicating the requested network event; and
generating, using the event fanning platform, an additional consumer application data stream including the requested network event for the additional consumer application.
5 . The method of claim 1 , further comprising:
determining a network event environment for deploying the consumer application; and
generating the consumer application data stream specific to the network event environment of the consumer application.
6 . The method of claim 1 , further comprising:
detecting a deprecation of the consumer application by detecting a user interaction deleting the consumer application from the network event data streaming platform; and
deprecating the consumer application data stream by automatically unbinding server resources allocated to the consumer application data stream in response to detecting the deprecation of the consumer application.
7 . The method of claim 1 , further comprising:
detecting a modification to the event request indicating an additional requested network event from among the plurality of network events hosted by the network event data streaming platform; and
based on the modification to the event request, generating an updated consumer application data stream using the event fanning platform indicating the requested network event and the additional requested network event.
8 . A system comprising:
at least one processor; and
a non-transitory computer readable medium storing instructions that, when executed by the at least one processor, cause the system to:
receive, from a consumer application, an event request indicating a requested network event from among a plurality of network events hosted by a network event data streaming platform;
generate, using an event fanning platform in response to the event request, a consumer application data stream specific to the requested network event and tied to a lifecycle of the consumer application;
provide, using the event fanning platform, the requested network event to the consumer application via the consumer application data stream; and
in response to detecting a deprecation of the consumer application, deprecate the consumer application data stream within the event fanning platform.
9 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to receive the event request indicating the requested network event by:
receiving an application configuration file defining the consumer application; and
detecting, within the application configuration file, a code segment defining the requested network event.
10 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to generate the consumer application data stream by using the event fanning platform to generate a data stream configuration file defining the consumer application data stream to include the requested network event.
11 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to:
receive, from an additional consumer application, an additional event request indicating the requested network event; and
generate, using the event fanning platform, an additional consumer application data stream including the requested network event for the additional consumer application.
12 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to:
determine a network event environment for deploying the consumer application; and
generate the consumer application data stream specific to the network event environment of the consumer application.
13 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to:
detect a deprecation of the consumer application by detecting a user interaction deleting the consumer application from the network event data streaming platform; and
deprecate the consumer application data stream by automatically unbinding server resources allocated to the consumer application data stream in response to detecting the deprecation of the consumer application.
14 . The system of claim 8 , further storing instructions that, when executed by the at least one processor, cause the system to:
detect a modification to the event request indicating an additional requested network event from among the plurality of network events hosted by the network event data streaming platform; and
based on the modification to the event request, generate an updated consumer application data stream using the event fanning platform indicating the requested network event and the additional requested network event.
15 . A non-transitory computer readable medium storing instructions that, when executed by at least one processor, cause a computing device to:
receive, from a consumer application, an event request indicating a requested network event from among a plurality of network events hosted by a network event data streaming platform;
generate, using an event fanning platform in response to the event request, a consumer application data stream specific to the requested network event and tied to a lifecycle of the consumer application;
provide, using the event fanning platform, the requested network event to the consumer application via the consumer application data stream; and
in response to detecting a deprecation of the consumer application, deprecate the consumer application data stream within the event fanning platform.
16 . The non-transitory computer readable medium of claim 15 , further storing instructions that, when executed by the at least one processor, cause the computing device to receive the event request indicating the requested network event by:
receiving an application configuration file defining the consumer application; and
detecting, within the application configuration file, a code segment defining the requested network event.
17 . The non-transitory computer readable medium of claim 15 , further storing instructions that, when executed by the at least one processor, cause the computing device to generate the consumer application data stream by using the event fanning platform to generate a data stream configuration file defining the consumer application data stream to include the requested network event.
18 . The non-transitory computer readable medium of claim 15 , further storing instructions that, when executed by the at least one processor, cause the computing device to:
receive, from an additional consumer application, an additional event request indicating the requested network event; and
generate, using the event fanning platform, an additional consumer application data stream including the requested network event for the additional consumer application.
19 . The non-transitory computer readable medium of claim 15 , further storing instructions that, when executed by the at least one processor, cause the computing device to:
determine a network event environment for deploying the consumer application; and
generate the consumer application data stream specific to the network event environment of the consumer application.
20 . The non-transitory computer readable medium of claim 15 , further storing instructions that, when executed by the at least one processor, cause the computing device to:
detect a deprecation of the consumer application by detecting a user interaction deleting the consumer application from the network event data streaming platform; and
deprecate the consumer application data stream by automatically unbinding server resources allocated to the consumer application data stream in response to detecting the deprecation of the consumer application.