Diahook
Dev tools
webhook delivery service
SHOW HN2021
How HN took it
15 positive, 16 neutral or asking, 5 mixed, 6 critical, out of 42 comments about the project. Thread score +0.27.
Idea: 10 for, 3 againstPrivacy: 1 for, 1 againstPerformance: 0 for, 2 againstExecution: 1 for, 0 againstPricing: 1 for, 0 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Saves building webhook infrastructure from scratch
From 3 comments
Spent so much time rolling my own webhook system for my eSign side project [0]- there are so many edge cases and thorny behaviors. This is a rare perfect fit of a SaaS offering.…
jackconsidine on HNI can't remember how many times I've written Redis-backed retry timers in Go to handle unreliable endpoints. It'd be great to not have to do that again. I like that you're…
wyc on HNA go-to architecture topic of mine for backend engineer interviews is to design a webhook system (the push side). I’ve gotten a lot of mileage out of it because depending on the…
jabo on HN
Easy integration
From 1 comment
We connected with Tom just as we were getting ready to build webhooks into our product (Kitemaker W21). We had a few teams asking for webhooks but didn’t have much time to…
kevsim on HN
Objections
Adds another service that can fail; uptime concern
From 2 comments
This looks nice but don't I still have to invest all the engineering to make sure my calls reach Diahook service in the first place? The argument from diahook seems to be "we'll…
owaislone on HNThis is great if it has a better uptime than the service that receive the message. On the other hand: now we have 2 Services that could crash and our app still need a retry…
progx on HN
Could be a library instead of a service
From 1 comment
This looks nice but don't I still have to invest all the engineering to make sure my calls reach Diahook service in the first place? The argument from diahook seems to be "we'll…
owaislone on HN
Requests
Exponential backoff and retry to alternate endpoints
From 2 comments
Thanks for asking: 1. Exponential backoff. We don't notify clients, but we notify you with a webhook. We actually don't have it implemented yet, but will have in the next week or…
tasn on HNOur whole focus is uptime, and I think it's similar to how you use other APIs in your service, how do you deal when you can't reach them? With that being said, this is something…
tasn on HN
Self-hosted option
From 1 comment
Thanks, I'll keep it in mind when we are ready! I especially like the easy postgres replication. :) I'll reach out about Diahook, as we can also have a self-hosted offering, and…
tasn on HN
Questions
How are failed requests to the API handled?
From 1 comment
I can't remember how many times I've written Redis-backed retry timers in Go to handle unreliable endpoints. It'd be great to not have to do that again. I like that you're…
wyc on HN
Does it offer 100% uptime?
From 1 comment
This looks nice but don't I still have to invest all the engineering to make sure my calls reach Diahook service in the first place? The argument from diahook seems to be "we'll…
owaislone on HN
Alternatives named
Hookdeck
From 2 comments
Nice work! I'm just glad to see more people in the space and there has been very little pressure on platforms to offer good webhooks, many integrations are pretty barebone and I…
alexbouchard on HNThanks a lot! And yeah, I'm familiar with hookdeck, your co-founder already commented in this thread. :)
tasn on HN
Zapier
From 1 comment
Zapier does it to an extent, but yeah, it's something to keep in mind. You got my creative juices flowing a bit with this comment, thanks a lot!
tasn on HN