3 ms·
> Drawback of Serverless: Vendor lock-in, statelessness, local testing, cold/warm start perf, security, deployment, execution, monitoring, remote testing, debug
by buf 9y ago
> Drawback of Serverless: Vendor lock-in, statelessness, local testing, cold/warm start perf, security, deployment, execution, monitoring, remote testing, debugging.
Excuse me? Let's use lambda for what it was meant to do, not replace your entire stack.
- gervase 9y agoBut 'serverless' has a much nicer ring to it than 'serverfewer'...
- wahnfrieden 9y agoWhat exactly do you think it’s meant to do? Amazon even lists web application backends as its first use case example in a recent article. All those things are necessary in production.
- bonesss 9y agoAll those issues can be postfixed with "... on Lambda". They're specific challenges that will come up when using Lambda as advertised in production :) As with most system improvements we're not really talking about removing complexity, just reshuffling it into a new and more pleasing form. Lambda will let you wildly simplify some things, but pain points otherwise accounted for in larger deployments will get moved onto your lambda services to compensate. Cold starts, for example, aren't generally an issue at the function level in web applications as the application itself is/isn't warmed up. By introducing a Lambda back-end you get to take a stance on that per-function while caring less about it in your webapp front-ends. The OP is trying to highlight where these new and less obvious challenges arise in the new stack, not pushing Lambda as the end all of app dev.
- Cthulhu_ 9y agoI'd expect a lot of those are things that should be supplied by AWS, especially things like providing a service that runs the code exactly as it would on AWS itself (which should fix the testing / debugging); monitoring and security should mostly be builtin.
- wahnfrieden 9y agoAWS does have solutions to many of these: SAM Local, X-Ray, Codestar, for instance.