Member-only story
Journey Of A Microservice Application In The Kubernetes World
Presentation of webhooks.app
TL;DR
webhooks.app is an open source application following the microservice architecture. Its purpose is to provide a webhook endpoint for demos. In this series of articles, I will present the application and several steps I used (and will use) to have it running in production in a Kubernetes cluster.
About this series
This series will be divided into the following articles detailing the purpose of the webhooks application: its architecture, how to deploy it locally and on a Kubernetes cluster, as well at the various project it relies on. Other articles might be added on topics that come to mind while writing.
- Presentation of the webhooks.app (the current article)
- Running the application on Kubernetes using Helm
- Running the application on a Civo Kubernetes cluster
- Continuous Deployment using GitOps with ArgoCD
- Observability using the Loki stack
- Defining the application using Acorn
- Security considerations : security related tools
- Security considerations : fixing misconfigurations
- Security considerations : policies enforcement
- Security considerations : vulnerability scanning (coming soon)
About the application
webhooks.app is an application whose purpose is to provide always-on secure webhook endpoints (basically a server waiting to receive json payload from a HTTP POST request). Webhook is a way for applications to communicate with each other, usually exchanging information as a json payload.
Let’s consider the following example: we have a Harbor container registry and want to be notified each time a new image is pushed to a given project. Harbor allows to specify a webhook (url and authentication token) and will send a json payload to this webhook each time a new image is pushed.
