Good article, and I think it's a sign we're approaching the trough of disillusionment w.r.t. serverless architecture. Just like with microservices, the benefit

Good article, and I think it's a sign we're approaching the trough of disillusionment w.r.t. serverless architecture. Just like with microservices, the benefits come from not using it as a giant hammer for everything, but in isolated use cases where it's actually a good fit. These are few and far between for serverless and the first challenge is making the right decision of when to use it. I do agree about vendor lock-in, but at the end of the day this is inescapable because of its very nature. It was always meant to be "run this code on someone else's infrastructure without me having to worry about maintaining it", so vendors are free to choose how that actually happens. What we need to fix this are standards that can be adopted by all vendors, so that it's easier to migrate. Something like OCI for serverless that isn't tied to specific runtimes would be ideal.