3 ms·

I understand the idea, but I don't understand why your product is easier to use than aws lambda

• cheerioty 4y ago
  Thanks mate. The difference is that you wouldn't really want to simply copy code from your customers/3rd parties for a couple of reasons: Missing out-of-the-box security/sandboxing, the time it takes to deploy and (cold) startup time. With Scriptable, you don't need to worry about any of that. And there’s nothing for you to provision or maintain apart from saving the user-provided scripts in your database.
  • aflag 4y ago
    How is aws lambda less of a sandbox? What can they do with lambda that they wouldn't be able to with scriptable?
    • hitsthings 4y ago
      You'd have to ensure they didn't have any privileges, for a start. E.g. you have to ensure you set the role correctly so they can't execute other lambdas in your account, etc. If you are running multiple users on the same lambda, one could potentially read filesystem data that another saved, for example (if the lambda hasn't restarted). You also probably want to make sure each user has individual compute limits, so one user can't execute 1000 scripts/second and DDOS other users. There's probably a lot of little things to think through (that I have not).