Re:Going Serverless with AWS Lambda and API Gateway
by hehheh on Tuesday August 16, 2016 @02:18PM
(#12299391)
Migration between infrastructures is always painful, so I don't think vendor lock in is that big a deal, if you keep APIs small and their I/O well documented (and designed).
[ Parent
| on HN ]
Re:Going Serverless with AWS Lambda and API Gateway
by kuschku on Tuesday August 16, 2016 @03:38PM
(#12300025)
Migration between a OVH VPS, a local server, or a Hetzner rootserver is not really painful.
I choose a preinstalled distro, deploy my script to automatically handle dependencies and set up the container infrastructure, pull the containers, and I have a server set up and able to run my containers in about 3 minutes, and connected to a central server so it can be provisioned containers to run.
The entire infrastructure can obviously be moved to another hoster in days, because the hoster is just providing a machine.
Re:Going Serverless with AWS Lambda and API Gateway
by interactiv on Tuesday August 16, 2016 @03:46PM
(#12300086)
> Migration between infrastructures is always painful, so I don't think vendor lock in is that big a deal, if you keep APIs small and their I/O well documented (and designed).
hmm, not if the only thing you have to do it upload an image on a server, there is nothing difficult with it. And yes the vendor lock in is a big deal unless all you write is throw away code. But it looks like it's the purpose of "Serveless servers", throw away apps ...