Our great sponsors
-
-
Healthchecks
Open-source cron job and background task monitoring service, written in Python & Django
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Obviously Deno have vested interest it (and so do I as the founder of Svix[1]), but my take is that webhooks are great, though there are alternatives that could be better or complementary depending on the situation.
At Svix we also support running JS instead of sending webhooks (using Deno!), and it is very useful, but there are many limitations with this approach, and in general oftentimes people just want the data passed to their systems and deal with it there. Not write a bit of JS to do something ad-hoc.
So in short, like always with software engineering: "it depends" and there are tradeoffs to each approach.
1: https://www.svix.com
In fact, your platform (https://healthchecks.io/) is a prime example of where running customer wasm would be really excellent.
Instead of sending webhooks out to customer configured URLs, you could run a Wasm environment to execute customer code. Off hand, a good use case here is to do further inspection of the event before it gets sent off to some other system - maybe there are cases where you send false-positives and needlessly trigger external system alerts. The customer Wasm could do more introspection on the healthcheck event and make a more informed decision about how to proceed.