There is absolutely no lock in whatsoever with Lambda. The features provided by Lambda are also provided by Google Cloud Functions and Azure Functions.
The lock in comes from the ecosystem you use them in. If you make code that just returns the time, you can run that anywhere. If you make code that uses a database, your database choice provides lock in, but not Lambda.
And it's the same lock in you get using any service from AWS.
But your trade off is that you can make something that's super portable, but must cater to the lowest common denominator of features amongst all the providers you want to be compatible with.
I'd rather have lock in than be hamstrung by the velocity of the slowest provider.
The lock in comes from the ecosystem you use them in. If you make code that just returns the time, you can run that anywhere. If you make code that uses a database, your database choice provides lock in, but not Lambda.
And it's the same lock in you get using any service from AWS.
But your trade off is that you can make something that's super portable, but must cater to the lowest common denominator of features amongst all the providers you want to be compatible with.
I'd rather have lock in than be hamstrung by the velocity of the slowest provider.