Webhooks use for a microservice architecture application
Disclosed embodiments are directed at systems, methods, and architecture for configuring event hooks in a microservice architecture-based system. The control plane links a plurality of APIs for a microservice architecture application. Each API includes a data plane proxy that serves traffic for the API from the control plane. The control plane receives an event hook including an event, a source, and a handler. The control plane configures a component of the microservice-architecture-based system to run the handler when the event occurs at the source. When the event occurred at the source, the component runs the handler.
1. A method comprising:
establishing a microservice architecture application including a plurality of services, wherein the plurality of services are each an application program interface (API) performing a piecemeal function of an overall application function, each service including a data plane proxy that reports operation of the service to an application control plane;
receiving an event hook that configures a first service of the plurality of services, wherein the event hook comprises an event, a source, and a handler; and
configuring the first service of the plurality of services with the event hook, wherein the configuration causes the first service to run the handler responsive to receiving the event from the source.
2. The method of claim 1 , further comprising:
receiving, from an external application, a notification that the event occurred at the source.
3. The method of claim 2 , wherein the external application is a messaging program.
4. The method of claim 1 , further comprising:
responsive receiving a notification that the event occurred at the source, sending a request to an external application.
5. The method of claim 4 , wherein the request is a preformatted POST request.
6. The method of claim 1 , further comprising:
responsive to receiving a notification that the event occurred at the source, building a request using a verb, a header, and a payload.
7. The method of claim 6 , wherein the request is a custom HTTP request.
8. The method of claim 1 , further comprising:
responsive to receiving a notification that the event occurred at the source, logging the event and a payload at a database of the application control plane.
9. The method of claim 1 , further comprising:
responsive to receiving a notification that the event occurred at the source, triggering a Lua function.
10. A system comprising:
a computer processor; and
a non-transitory computer-readable storage medium storing instructions that when executed cause the computer processor to perform actions comprising:
establishing a microservice architecture application including a plurality of services, the plurality of services are each an application program interface (API) performing a piecemeal function of an overall application function, each service including a data plane proxy that reports operation of each service of the plurality of services to an application control plane;
receiving an event hook that configures a first service of the plurality of services, wherein the event hook comprises an event, a source, and a handler; and
configuring the first service of the plurality of services with the event hook, wherein the configuration causes the first service to run the handler responsive to receiving the event from the source.
11. The system of claim 10 , further comprising: receiving, from an external application, a notification that the event occurred at the source.
12. The system of claim 11 , wherein the external application is a messaging program.
13. The system of claim 10 , further comprising:
responsive receiving a notification that the event occurred at the source, sending a request to a third party system.
14. The system of claim 13 , wherein the request is a preformatted POST request.
15. The system of claim 10 , further comprising:
responsive to receiving a notification that the event occurred at the source, building a request using a verb, a header, and a payload.
16. The system of claim 15 , wherein the request is a custom HTTP request.
17. The system of claim 10 , further comprising:
responsive to receiving a notification that the event occurred at the source, logging the event and a payload at a database of the application control plane.
18. The system of claim 10 , further comprising:
responsive to receiving a notification that the event occurred at the source, triggering a Lua function.
19. A method comprising:
receiving, at a first service of a plurality of services connected via a microservice architecture application, a request for utilization of the first service, wherein the plurality of services are each an application program interface (API) performing a piecemeal function of an overall application function, each service including a data plane proxy that reports operation of the service to an application control plane;
receiving, at the first service from the application control plane, configuration instructions associated with an event hook, wherein the event hook comprises an event, a source, and a handler; and
responsive to receiving the event from the source, running the handler at the first service.
20. The method of claim 19 , wherein the source is an application external to the microservice architecture application.