3 ms·
After using lambda and serverless myself over the past year, I really struggle to see where this lock-in is. If you're already writing a stateless API as most a
by adjkant 8y ago
After using lambda and serverless myself over the past year, I really struggle to see where this lock-in is. If you're already writing a stateless API as most are these days, and the cloud platforms support many language options, going between say EC2 and Lambda really isn't that much difference in code. If that changeover time is too costly for you, that's far more likely a sign of changing infrastructure too often.
- robrtsql 8y agoIn my opinion, the real lock-in is not the stateless API, but the tie-ins with other AWS services that may end up being required to accomplish what you need. Like, if you're trying to provide a calculator API, you can definitely run that in Lambda and then easily move it somewhere else when AWS does something to upset you. But, let's say you're trying to do something a little more complicated (a common example is validating and transforming profile pictures for some sort of app), you might end up using AWS Step Functions and SQS. Your code is still portable but it relies on a bunch of managed services.