Some do; Gitlab, Otka, and Pipedrive come to mind. I think this is more about the expectations set over the last decade. If you do things differently, there's a need to justify it, and it's just perceived as less secure, regardless of whether it's true or not (the pros and cons are well articulated in the article).
I expect to have to answer that question a lot! Hookdeck is an event gateway, an unopinionated event log/message bus that operates over HTTP. It can be used to send webhooks, but 80%+ of use cases are for inbound webhooks (consumer side).
We think outbound is best served with an opinionated, purpose-built product, as the use case is very specific. The common feedback we got from event producers is that they are all annoyed by the complexity and costs of their current solution for sending webhooks. We think OSS / self-hosted is the solution to that. We drew from our experience handling 100 billion events, but also kept the scope to the table stakes to be highly efficient and simple to operate.
Event destinations' support is also crucial here because it means more efficient delivery with fewer errors, which can drastically reduce the overhead of event delivery.
From most watch market positioning I'd assume this to be true. However for me it's the exact opposite, the watch is a tool to cut phone use. All I care about is LTE and the minimum I need to get around the world. SMS, calls, WhatsApp, Gmaps. All existing decent looking watch have atrocious battery life to offer all the health features.
Been looking for something like this! Doc search just hasn't kept up with what's possible now and is such a hassle to get the indexing to work properly. Will try it out!
YAML is just as effective at communicating data structure to the model while using ~50% less tokens. I now convert all my JSON to YAML before feeding it to GPT API's
Hookdeck is an infrastructure to consume webhooks simply & reliably. Incoming webhooks are challenging because they require a well-built (and often complex) asynchronous system. We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.
If you are looking to be part of a early stage team, fully leverage your knowledge & talent, have an impact on the product experience and implement features from scratch then this might be for you!
We are offering competitive compensation, generous stock options and liberty over your geo & schedule.
We are looking forward to hearing from you! Email me at [email protected]
Hookdeck is an infrastructure to consume webhooks reliably. Incoming webhooks are challenging because they require a well-built (and often complex) asynchronous system. We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.
If you are looking to be part of an early (funded) team, fully leverage your knowledge & talent, have an impact, and work on hard scaling and concurrency challenges, this might be for you.
We are offering competitive compensation, generous stock options and liberty over your geo & schedule.
We are looking forward to hearing from you! Email me at [email protected]
PH takes much more work and strategy but "success" is somewhat deterministic if you did your homework. In our case we saw similar uptake, signups and conversion then ~20h on HN front page over the course of a week. PH had a much higher half-life and we saw stable uptake for a few days while HN was all in the first few hours.
It was definitely worth it for us. Some of our best customers found us on PH and our lead investor first heard of us during our launch and reached out.
That's right. In the context of pushed events, you have very little margin for error. It's definitely "solvable," but a bit part of the problem is that for most tech teams, it's not their bread and butter. Handling webhooks reliably is just overhead and work they aren't putting into their actual product. So you end up with a lot of not-so-reliable implementations.
I'm all for /events and appreciate the platforms with good support. However, we live in a world where people build event-driven and serverless architecture. The use cases go beyond replication, and webhooks are here to stay.
The thing is, you can get the best of both worlds by using webhooks in conjunction with /events reconciliation. That might seem like a lot of work, but that's what tooling is for. Webhooks are complicated to handle reliably, but it's a problem that has good tools the same way sequin (and many others) is helping developers solve the replication problem.
For webhooks, hookdeck.com (disclaimer, I'm the founder) address entirely the problems stated and will soon offer automatic reconciliation (currently running our polling Beta on with Shopify API)
Hookdeck is an infrastructure to consume webhooks simply & reliably. Incoming webhooks are challenging because they require a well-built (and often complex) asynchronous system. We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.
If you are looking to be part of an early (funded) team, fully leverage your knowledge & talent, have an impact, and work on hard scaling and concurrency challenges, this might be for you.
We are offering competitive compensation, generous stock options and liberty over your geo & schedule.
We are looking forward to hearing from you! Email me at [email protected]
Exactly, 6% of GPD is shockingly low cost to pay for net 0 annual growth in CO2. Now that doesn't mean you can practically deploy that capital but it makes me more bullish on carbon removal.
Hookdeck is looking for a backend and reliability engineer to improve Hookdeck core platform and infrastructure. We are a small team of 3 operating completely remotely and without schedule.
We help developers spend less building and troubleshooting issues with their webhooks to focus on their products instead. We offer a complete infrastructure to develop, test, receive, distribute and monitor webhooks and asynchronous events.
If you are looking to be part of a early founding team, fully leverage your knowledge & talent, have impact and work on hard scaling and concurrency challenges then this might be for you.
We are offering competitive compensation & generous stock options.
Looking forward to hearing from you! Email me at [email protected] :)
Sweet! For payment and billing related webhooks, the total count of events tends to be relatively low. I can't help with an estimate per se without more context, but the team plans allow for 5 million webhooks, and the overage is 5$ per million. Does that sound reasonable? In any case, reach out to me, and I'd be happy to go into the details :) (contact in profile)
Hey! Yes we do, you can either verify the webhooks yourself as you normally would (we do not alter the payload, usual verification will work) or have Hookdeck verify the signature and resign it with a Hookdeck signature associated with your workspace.
For Stripe specifically, the later is best because of the encoded timestamp in the hmac signature and that's what we do for our own Stripe webhooks.
It boils down to the number of dependencies you have and the uptime of those dependencies. For instance, you'll need to write to some form of temporary or permanent storage like SQS, S3 or PG. What happens when this is down, or you've busted your connection limit? With webhooks, you have no control over the throughput, and enormous bursts of traffic are frequent.
You can build reliable ingestion, and we aren't reinventing the wheel on that front. The difference is that we've taken the time, and many teams prefer to invest that time elsewhere.
We can also take some extra steps (and will), such as having multiple $Provider as fail-over.
[EDIT]
To add to this, Hookdeck ingestion reliability is only part of the value proposition. What customers really appreciate is the visibility and error recovery. They don't have to build a robust asynchronous processing system. They can just deploy an HTTP endpoint and call it a day.