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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Webhooks: The Devil in the Details

53 点作者 cnj超过 8 年前

3 条评论

vertex-four超过 8 年前
So part of the issue here is that many message queue systems have rather terrible authentication, certain cloud-hosted systems aside - it often seems to be that authentication allows you to post any message you like and listen on any queue you like. A message queue designed for external entities to access would require far more rigorous security mechanisms.<p>I&#x27;d also suggest that it would want some form of federation - so instead of external entities pushing directly into your message queue, they&#x27;d push to theirs, and your message queue would pull from theirs and push to your consumers. That way, you don&#x27;t lose messages from your provider when your connection to them fails.
评论 #13132187 未加载
fiatjaf超过 8 年前
It is not as easy to get some thing running with a message queue as it is with webhooks. The API documentation would be complicated and large, also special libraries would be needed.
jlward4th超过 8 年前
Or a more simple solution... Have a webhook receiver send the messages to Kafka. Then you don&#x27;t have to change to a more complex delivery protocol.
评论 #13132051 未加载