Pramil Gawande

What is a Webhook? Here's an example to help you understand it. You have an application, and you want it to automatically do things without you having to trigger them manually. That's where webhooks come in! Webhooks are like messengers, allowing one system to send a message to another whenever a specific event happens. It's like getting a notification on your phone when someone comments on your social media post or when you receive an email. Webhooks work similarly but for systems and applications. Here's the basic flow: 1) Service A exposes a webhook 2) Service B subscribes to the webhook from Service A 3) Service A writes down the subscription 4) The event occurs in Service A 5) Service A sends the webhook request to Service B There are many ways that webhooks can be helpful. For example, you can use webhooks to automatically update a database or trigger an action when a form is submitted on your website. They can also be used to send notifications or alerts, such as when a new user signs up for your service or when an error occurs in your system. I once implemented a webhook in a text-to-speech API. The application exposes an endpoint to upload a text file, and you can also pass in a webhook URL. An AI model will process the text file in the background and convert it into an audio file. When the audio file is complete, the application will trigger the webhook. The client can then download the audio file or do something else. P.S. If you liked this, consider joining The .NET Weekly - my newsletter with 43,000+ engineers that teaches you how to improve at .NET and software architecture. Subscribe here → milanjovanovic.tech/?utm_sou… ❓ Bonus question How would you reliably handle sending multiple webhook requests?