5 ms·

Let's say I use some SaaS for handling payments and subscriptions. The SaaS can notify me via a webhook when a user successfully creates a subscription on their

by cuu508 3y ago

Let's say I use some SaaS for handling payments and subscriptions. The SaaS can notify me via a webhook when a user successfully creates a subscription on their hosted payment page, so I can, let's say, adjust their allowed features and resource limits on my end. If we throw away webhooks, how would this work with Wasm?

nilslice 3y ago
The SaaS can run your wasm code for you. In this case, you'd write the same code that you'd otherwise run in your infra to respond to the webhook, but it would be compiled to Wasm and run _in the SaaS app_ where the source event was triggered. In your specific case, you'd still be making a call-out to your system to adjust the entitlements as you describe. However, many cases are actually taking action back on the SaaS side via API calls to the SaaS. So instead of a handful of back-and-forth calls over the Internet between you and SaaS, you just call their functions from the Wasm code running in their infra.
- deleted 3y ago
  [deleted]
- tonyhb 3y ago
  So you have to give your 3rd party providers access to _code you write_, _secrets to your own datastores_, _open firewalls to 3rd parties_, and then allow them to run any code which could access your system, hoping that they do in fact run the blob you upload?
  - nilslice 3y ago
    pretty much everything of any level of sophistication require this. unsure what your point is. wouldn't your customers for inngest need to do the same for anything integrated?
    - goodoldneon 3y ago
      No, Inngest doesn't host your code so it doesn't need your secrets
      - nilslice 3y ago
        yet
- jddj 3y ago
  I've re-read this a few times to try to grasp the wisdom which the confident contrarian tone makes me suspect is in there. I have to say I couldn't find it. Could you give an example scenario where the status quo would be improved by uploading a wasm handler to a server instead of passing messages?
  - nilslice 3y ago
    Look at the Shopify Functions platform
nilslice 3y ago
In fact, your platform (https://healthchecks.io/ 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.

by cuu508 3y ago

nilslice 3y ago

The SaaS can run your wasm code for you. In this case, you'd write the same code that you'd otherwise run in your infra to respond to the webhook, but it would be compiled to Wasm and run _in the SaaS app_ where the source event was triggered. In your specific case, you'd still be making a call-out to your system to adjust the entitlements as you describe. However, many cases are actually taking action back on the SaaS side via API calls to the SaaS. So instead of a handful of back-and-forth calls over the Internet between you and SaaS, you just call their functions from the Wasm code running in their infra.

deleted 3y ago
[deleted]
tonyhb 3y ago
So you have to give your 3rd party providers access to _code you write_, _secrets to your own datastores_, _open firewalls to 3rd parties_, and then allow them to run any code which could access your system, hoping that they do in fact run the blob you upload?
- nilslice 3y ago
  pretty much everything of any level of sophistication require this. unsure what your point is. wouldn't your customers for inngest need to do the same for anything integrated?
  - goodoldneon 3y ago
    No, Inngest doesn't host your code so it doesn't need your secrets
    - nilslice 3y ago
      yet
jddj 3y ago
I've re-read this a few times to try to grasp the wisdom which the confident contrarian tone makes me suspect is in there. I have to say I couldn't find it. Could you give an example scenario where the status quo would be improved by uploading a wasm handler to a server instead of passing messages?
- nilslice 3y ago
  Look at the Shopify Functions platform

nilslice 3y ago

In fact, your platform (https://healthchecks.io/ 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.