The wonderful world of webhooks
summary
States that webhooks are pubsub over HTTP, not polling, so servers push events and clients just reply 200; GitHub webhooks include a verbose JSON payload (the “smallest” example still has 111 more lines) with URL, owner, avatar, content_type and secret, and require pre-arrangement. Advice is to accept and store then respond immediately (queue and process later). Shows practical wiring with Hubot and Zapier, and warns a minimal payload can trigger a Thundering Herd when millions of subscribers exist.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:26Webhooks in the Wild
- 1:04How APIs Work
- 1:24How Webhooks Work
- 2:10APls Over Time
- 3:14Webhooks Over Time
- 3:57Setup
- 5:16Inside A Webhook
- 7:21Receiving Webhooks
related talks
39mImplementing a Webhook, Not So Simple!
26mWebHooks vs WebSub: which one to stream your events in Real Time?
55mWorking with Webhooks
51mImplementing a server-side webhook, not so simple
47mImplementing a server-side webhook, not so simple!
41mTreading Water in a Stream of Data
31mWebhooks for Automated Updates [B]
46mREST, GraphQL, gRPC, Webhooks: when to use each?
