Webhooks are an amazing implementation.
As Arthurs says, they can fail (how many times have we seen Travis not triggered because the GitHub webhooks were out of order?), but they are extremely efficient.
Implementing on your own server is easy, and separating them into another service ensures performance on both sides.
On the receiving side, if your application is fault tolerant there should be no problem. A bad response should trigger a specific HTTP status code that will prompt the sender to stop and maybe notify their user (403 for example), and if you don't get an event, then there's nothing you can do, so no specific management there.
Every modern app should have some sort of webhook implmentation, whether receiving (GitHub, Zapier, Stripe...) or sender (Zapier, IFTTT, other business integrations).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Webhooks are an amazing implementation.
As Arthurs says, they can fail (how many times have we seen Travis not triggered because the GitHub webhooks were out of order?), but they are extremely efficient.
Implementing on your own server is easy, and separating them into another service ensures performance on both sides.
On the receiving side, if your application is fault tolerant there should be no problem. A bad response should trigger a specific HTTP status code that will prompt the sender to stop and maybe notify their user (403 for example), and if you don't get an event, then there's nothing you can do, so no specific management there.
Every modern app should have some sort of webhook implmentation, whether receiving (GitHub, Zapier, Stripe...) or sender (Zapier, IFTTT, other business integrations).