thanks a lot for this man!!!!!!!!!!!!!!!!!!!!!!!!!!!! I will check this later, for now just leaving a comment for the algorithm, I will definitely use this tutorial soon!!
I thought webhook is different than API. I assumed if client service is down then webhook will not care whether client has received the request or not. But here both are same. Even webhook wait s for the response. If client service is down webhook is also throwing error
Webhook always trigger for specific event but API is always common for all scenario. So if you want to send data during event trigger then use webhook. Even you can add an extra column in db, so if you sent webhook and received a response from the client then update as webhook sent. Best way is to send a webhook response in cronjob
So finally webhook it synchronous communcation right. inside one microservice calling another microservice service url right. I didn't find any diffrence apartfrom this.
but it has to be executed on the basis of the event. Generally if client having different end point url and they need data as per event of their url then you can use webhook. Webhook is just a way to send the data whenever the event occurred
you can't just redirect. You need to know that at which event you need to send a response where. Here for different events API will be different. Let me correct you, here response status will be 200
![Stromae, Pomme - “Ma Meilleure Ennemie” (from Arcane Season 2) [Official Visualizer]](http://i.ytimg.com/vi/1F3OGIFnW1k/mqdefault.jpg)
thanks a lot for this man!!!!!!!!!!!!!!!!!!!!!!!!!!!! I will check this later, for now just leaving a comment for the algorithm, I will definitely use this tutorial soon!!
I thought webhook is different than API. I assumed if client service is down then webhook will not care whether client has received the request or not. But here both are same. Even webhook wait s for the response. If client service is down webhook is also throwing error
Webhook always trigger for specific event but API is always common for all scenario.
So if you want to send data during event trigger then use webhook.
Even you can add an extra column in db, so if you sent webhook and received a response from the client then update as webhook sent.
Best way is to send a webhook response in cronjob
So finally webhook it synchronous communcation right. inside one microservice calling another microservice service url right. I didn't find any diffrence apartfrom this.
but it has to be executed on the basis of the event.
Generally if client having different end point url and they need data as per event of their url then you can use webhook.
Webhook is just a way to send the data whenever the event occurred
I think ur using a API passing another url, is that correct ? I tought it would be something like a beam config just like Swagger or something else
nope. Here you need to send the response so you have to use the API only. Regarding Beam, I really don't know, I need to check
@@TalentedDeveloper what u basicaly does in this its the redirect logic, the only diference is that the response status must be 302
you can't just redirect. You need to know that at which event you need to send a response where. Here for different events API will be different.
Let me correct you, here response status will be 200