3 ms·

> - Vendor lock-in Try something like https://github.com/apex/up https://github.com/apex/up - write the code as regular servers, and it'll convert your entire s

> - Vendor lock-in Try something like https://github.com/apex/up https://github.com/apex/up - write the code as regular servers, and it'll convert your entire server into a function. > - Cold/warm start Should be a temporary annoyance - I'm sure all the providers are already hard at work on fixing this. > - Security/monitoring Easier to do than regular servers - most FaaS systems have monitoring built in, and collect whatever you write to STDOUT. > - Debugging: Yeah, can't do much about that. > - Local testing Besides Up mentioned above, should see more and more shims like https://github.com/RealImage/concave/blob/master/server.js https://github.com/RealImage/concave/blob/master/server.js coming up. > - Deployment Still a mess, but give it time. Heroku like experiences for FaaS should be a matter of time.

Vinnl 9y ago
I didn't really feel like the benefits of packages like Serverless and Apex were worth it for me, as they're not solving that big of a problem, and you'd replace it with lock-in to even less mature products. That said, the current lock-in is not that bad, just good to be aware of and keep an eye on. I hope that the annoyances are temporary indeed, but that doesn't buy me anything today :) That said, I think for almost all my drawbacks it holds true that they're likely to grow less and less significant, so if serverless is not worth it for you today, it's still worth it to keep an eye on. Edit: I should perhaps also link the shim that I'm using. It's slightly longer, also specific to my relatively loose configuration of API Gateway, and also simulates S3's client-side file upload functionality. As you can see, it's really not that bad: https://gitlab.com/Flockademic/Flockademic/blob/dev/app.ts https://gitlab.com/Flockademic/Flockademic/blob/dev/app.ts
- sudhirj 9y ago
  Up != Apex, same developer, though. Apex embraces serverless as an architecture, Up runs regular servers as functions.
  - Vinnl 9y ago
    Oh, oops, didn't scan close enough. But in any case, I don't want to be writing "regular servers", I want to write FaaS functions. Ideally (and hopefully this is where we will end up), against the same interface regardless of provider, but not necessarily e.g. Express's interface. Thanks for sharing though, it's surely useful to some.

Vinnl 9y ago

I didn't really feel like the benefits of packages like Serverless and Apex were worth it for me, as they're not solving that big of a problem, and you'd replace it with lock-in to even less mature products. That said, the current lock-in is not that bad, just good to be aware of and keep an eye on. I hope that the annoyances are temporary indeed, but that doesn't buy me anything today :) That said, I think for almost all my drawbacks it holds true that they're likely to grow less and less significant, so if serverless is not worth it for you today, it's still worth it to keep an eye on. Edit: I should perhaps also link the shim that I'm using. It's slightly longer, also specific to my relatively loose configuration of API Gateway, and also simulates S3's client-side file upload functionality. As you can see, it's really not that bad: https://gitlab.com/Flockademic/Flockademic/blob/dev/app.ts https://gitlab.com/Flockademic/Flockademic/blob/dev/app.ts

sudhirj 9y ago
Up != Apex, same developer, though. Apex embraces serverless as an architecture, Up runs regular servers as functions.
- Vinnl 9y ago
  Oh, oops, didn't scan close enough. But in any case, I don't want to be writing "regular servers", I want to write FaaS functions. Ideally (and hopefully this is where we will end up), against the same interface regardless of provider, but not necessarily e.g. Express's interface. Thanks for sharing though, it's surely useful to some.