Re:Give me /events, not webhooks
by stickfigure on Saturday January 08, 2022 @01:32PM
(#29854614)
You have no control over how often clients will poll even if you have webhooks. But it's easy enough to cache /events in cheap ephemeral storage, possibly even at the http level. Use Cloudflare if you want cheap. There shouldn't be much of an engineering cost here.
[ Parent
| on HN ]
Except that webhooks are often client-private. Consider, for example, GitHub repository webhooks, particularly for private repositories. Storing /events in a global CDN cache is a privacy nightmare. The GitHub API has strict usage quotas and I'm sure that the engineering effort for doing that at GitHub's scale is non-trivial.
Re:Give me /events, not webhooks
by stickfigure on Saturday January 08, 2022 @04:12PM
(#29856342)
So you make the API /clients/CLIENTID/events. What's the issue?
Webhooks have engineering issues all their own, including job queues and failure notifications. Stashing events in a table and truncating it every now and then is relatively straightforward.