Re:Collection of best practices for providing and consuming ...
by floucky on Friday August 19, 2022 @04:13AM
(#32518587)
Emails 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
Re:Collection of best practices for providing and consuming ...
by tasn on Friday August 19, 2022 @08:09AM
(#32520006)
We 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. ;)
Re:Collection of best practices for providing and consuming ...
by caseysoftware on Friday August 19, 2022 @09:41AM
(#32520814)
That'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: [email protected]
Re:Collection of best practices for providing and consuming ...
by tasn on Friday August 19, 2022 @09:46AM
(#32520880)
Will email you now in a bit! I also just replied to your other comment about another topic, so there's much to discuss. :)
Re:Collection of best practices for providing and consuming ...
by Traubenfuchs on Friday August 19, 2022 @11:43AM
(#32522427)
> What alternatives are there?
At the top of my head: Short Polling, long polling, websockets, response streaming, SSE, SNS, paging API, comet...
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/ * ???