4 ms·
As this page makes very clear, it's actually pretty hard to make a robust webhooks implementation! What alternatives are there? I've looked at: * Publishing AW
by sparsely 4y ago
As this page makes very clear, it's actually pretty hard to make a robust webhooks implementation!
What alternatives are there? I've looked at:
* Publishing AWS EventBridge events to other accounts.
* /events instead of webhooks https://blog.sequin.io/events-not-webhooks/ https://blog.sequin.io/events-not-webhooks/
* ???
- floucky 4y agoEmails maybe ? But it means you have to regularly check your inbox. Or use a webhook called by your email provider when you receive an email :D
- tasn 4y agoWe built Svix[1] exactly for this reason. We make it super easy for companies to send webhooks reliably. There are only three companies with a "perfect score" on webhooks.fyi's list, we power one of them. ;) [1] https://www.svix.com https://www.svix.com
- caseysoftware 4y agoThat's awesome and glad to see others making it easier and better to do this right. Obviously you should add some of your other customers to make sure they get the attention they deserve. Also, there are other patterns or practices that should be in the list, let us know. PRs are welcome but feel free to email me directly: danger@ngrok.com
- tasn 4y agoWill email you now in a bit! I also just replied to your other comment about another topic, so there's much to discuss. :)
- Traubenfuchs 4y ago> What alternatives are there? At the top of my head: Short Polling, long polling, websockets, response streaming, SSE, SNS, paging API, comet...