AWS Lambda also supports running containers. And it supports a number of language runtimes. Including custom runtimes. The only think proprietary it imposes is

AWS Lambda also supports running containers. And it supports a number of language runtimes. Including custom runtimes. The only think proprietary it imposes is the interface your function reads in when it is called. I'm curious what part of Lambda makes it have excessive lock-in vs the others once you discount "choosing to consume dozens of proprietary services"? All my serverless code always has a wrapper function to decide the request object so porting it to another cloud provider (even from Lambda) is pretty easy. Edit: The article seems to state the issue is that things like step functions are proprietary but: a. That's not lambda b. Don't use step functions, no one is forcing you. There is nothing step functions does that can't he handled other ways.