3 ms·
Am I the only one put off by the AWS (S3+Lambda) lock-in they seem to be creating for themselves?
by rndgermandude 6y ago
Am I the only one put off by the AWS (S3+Lambda) lock-in they seem to be creating for themselves?
- rsstack 6y agoIt should only take a couple of days to switch those to a different cloud provider. When building a Jamstack website there is only very thin logic in the Lambda itself, and S3 is only used as managed file storage.
- lawwantsin17 6y agoThis is the same hand waving everyone does. There is lock in. To be sure, with developing any system.
- fallat 6y agoand GitHub...
- GoblinSlayer 6y agoAnd kubernetes, and react, and mysql. How to add something apple to the mix?
- adrianmalacoda 6y agoAre they locked into github (using their proprietary APIs) or just using it as a git backend (using standard git tooling)? It's not clear from the article.
- stu2b50 6y agoI'm pretty confident they're going to handle PRs via the github interface. I don't think they'd get many contributions if you had to email patches in.
- rndgermandude 6y agoright, tho the github lock-in is probably gonna be the least worse if they mostly rely on git itself (GH issues and PRs can be migrated to other providers or self-hosted a lot more easily than uncoupling yourself from AWS APIs and services).
- striking 6y agoS3 is just files and Lambda is just FaaS, you can host your own open source versions of these tools and not encounter an issue. This would be a more solid argument if they were using a lot of AWS features together, but you could replace this with Minio and FastCGI if you really wanted to.