Re:Optimizing Lambda Cost with Multi-Threading
by eropple on Monday December 14, 2020 @10:11AM
(#25418403)
> A Lambda deployment has the advantage that no one needs to manage it
I assure you that somebody does need to manage it, and if nobody is you are going to eventually hit the wall at speed.
I've been called into SEV-1 issues where a Lambda-based web app spontaneously disappeared. (Seasoned AWS heads can probably make a guess as to why.)
Re:Optimizing Lambda Cost with Multi-Threading
by Autowired on Monday December 14, 2020 @10:17AM
(#25418471)
Sure, I was perhaps too hyperbolic. In my case, the advantage was specifically fault isolation for a multi-tenant, low traffic, demanding workload that was traditionally deployed as a physical service.
A Lambda deployment has the advantage that no one needs to manage it, and faults are isolated between clients. You could argue that if you need these properties your engineering organization has deeper flaws, and you'd be right, but in many companies engineers need to make do with what they get.