2 ms·
One way to get around vendor lock-in if you're worried about it, is to use a shim that translates the proprietary code to a basic http interface. So you just wr
by iamtomcat 8y ago
One way to get around vendor lock-in if you're worried about it, is to use a shim that translates the proprietary code to a basic http interface. So you just write your code as it it were a basic interface. There are tools like apex up, https://github.com/apex/up https://github.com/apex/up which do this already, though at the moment only support aws, but could eventually be setup to push to any provider.
- styfle 8y agoAnother alternative is ZEIT Now 2.0 which is supposed to be cloud-agnostic serverless. It puts a few more layers of abstractions between the developer and the cloud providers. https://zeit.co/blog/now-2 https://zeit.co/blog/now-2
- omnimus 8y agoPeople will argue that there is vendor locking with Now 2.0 - it has its own config file and way of doing this. But i am running express and the config is tiny, just few lines. If you use some cloud db provider for db that you can host yourself (like postgres or mongo in my case). You can move to your infrastructure without any pain. Mind you using Express is not the "ideal" way Zeit seems to push. It is exactly like with PHP - you are supposed to use simple files and leave routing to webserver. I think they forget that there is no PHP framework that uses this. All of them use the "Front controller" pattern and webserver basically routes everything to it. There must be reason for this.
- checker 8y agoThe Serverless Framework https://serverless.com/framework/ https://serverless.com/framework/ consolidates the functionality of all the major cloud providers behind one API, greatly reducing lock-in. Agree though, when you’re talking about Lambda it should just be another entry point into your business logic.