TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: What Comes After Webhooks?

17 点作者 abeaclark超过 3 年前
I feel like it&#x27;s time for an improvement on &#x2F; replacement for webhooks.<p>Pains &#x2F; concerns:<p>* Local development is annoying (ngrok, etc.)<p>* Security is low<p>* Doesn&#x27;t work super well with serverless stack<p>Curious how others are thinking about this.

7 条评论

anderspitman超过 3 年前
This is an article on the subject I really enjoyed recently: <a href="https:&#x2F;&#x2F;blog.sequin.io&#x2F;events-not-webhooks" rel="nofollow">https:&#x2F;&#x2F;blog.sequin.io&#x2F;events-not-webhooks</a>
评论 #29846417 未加载
binarynate超过 3 年前
I agree that local development is annoying, but I haven&#x27;t found the other two to be pain points:<p>- For security, services that invoke webhooks usually cryptographically sign their payloads to allow their authenticity to be verified.<p>- Maybe you mean something else by serverless, but in my experience, it has been relatively easy to deploy an AWS Lambda function (e.g. using Serverless Framework) that gets called by a webhook.<p>Webhooks aren&#x27;t perfect, but they do seem significantly simpler than the alternatives that come to mind, like WebSockets or WebRTC. Long polling is simpler, but often that is already an option for services that provide webhooks. I&#x27;ll be interested to see if others have ideas for better alternatives, though.
评论 #29846638 未加载
jka超过 3 年前
No answers, but since you asked about ways to think about the problem, here&#x27;s one interpretation:<p>- An HTTP request is like a function call (a named function, with arguments as path&#x2F;params&#x2F;body)<p>- A webhook is like a callback (albeit across a network boundary)
hbcondo714超过 3 年前
I guess &quot;Webhooks as a service&quot; would come next and alleviate some of these issues. As discussed here: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=27528202" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=27528202</a><p>Some of my customers also use these:<p><a href="https:&#x2F;&#x2F;zapier.com&#x2F;page&#x2F;webhooks&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zapier.com&#x2F;page&#x2F;webhooks&#x2F;</a><p><a href="https:&#x2F;&#x2F;support.discord.com&#x2F;hc&#x2F;en-us&#x2F;articles&#x2F;228383668-Intro-to-Webhooks" rel="nofollow">https:&#x2F;&#x2F;support.discord.com&#x2F;hc&#x2F;en-us&#x2F;articles&#x2F;228383668-Intr...</a>
评论 #29846673 未加载
ryanmccullagh超过 3 年前
Places like MailGun that don&#x27;t support any type of authentication. Stripe and GitHub do it well.
wizwit999超过 3 年前
We&#x27;re working on a solution to solve a lot of this, especially for event data. We push events directly to your customers, so they neither need to pull them or build webhook endpoints. Contact me if your interested.
schappim超过 3 年前
This would be what AWS’ Event Bridge and Event Bus are trying to solve. Pitty it is not a standard across multiple cloud providers.