The argument makes no sense. Because it is deployed in AWS, you can't get performance without using AWS services, therefor it is locking.
This seems like no more of a lockin than, say, choosing a DNS server that's giving me lower latencies.
My AWS Lambdas talk to a Postgres database, S3 (which has many open source API implementations), and SQS, which yeah, I'm "locked into".
The work to move to another service would be absolutely trivial. All of the AWS stuff like Postgres, S3, and SQS is totally abstracted from the business logic. I could rip it out at any time.
I just don't get what anyone means when they saw lambdas lock you in, I don't feel locked in at all. I could move to GCP in, idk, two weeks probably.
This seems like no more of a lockin than, say, choosing a DNS server that's giving me lower latencies.
My AWS Lambdas talk to a Postgres database, S3 (which has many open source API implementations), and SQS, which yeah, I'm "locked into".
The work to move to another service would be absolutely trivial. All of the AWS stuff like Postgres, S3, and SQS is totally abstracted from the business logic. I could rip it out at any time.
I just don't get what anyone means when they saw lambdas lock you in, I don't feel locked in at all. I could move to GCP in, idk, two weeks probably.