4 ms·

aka "Going towards total vendor lock in by basing your system on a proprietary, non portable infrastructure service"

hehheh 10y ago
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).
- kuschku 10y ago
  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.
- interactiv 10y ago
  > 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 ...
psuter 10y ago
FWIW, OpenWhisk, while available on IBM Bluemix, is also open source and can be run wherever you so desire: https://github.com/openwhisk/openwhisk https://github.com/openwhisk/openwhisk
- takeda 10y ago
  If you want to run it in aws you will still have to run it on a server. BTW: I really hate the marketing inventions. There's no cloud, or serverless, you still run your software on someone's server.
  - coredog64 10y ago
    I hear ya. The keyless entry on my Prius still requires me to carry a key.
    - takeda 10y ago
      That's a bit different, you have a different technology (although it still contains a key as a backup) and call it a key. Anyway the serverless is essentially (as someone here pointed out) the same idea as shared hosting which is very popular with php. It just uses a different name.
harryh 10y ago
Not if you build things in a thoughtful way. The code behind a REST call shouldn't really be all that different when deployed to Lambda vs run in a standalone binary on a rackspace server.
joecot 10y ago
There are a number of frameworks that should make migration between services pretty reasonable. Check out Serverless https://github.com/serverless/serverless https://github.com/serverless/serverless . It'll work for Lamba, google cloud, Azure, and IBM Whisk If you look at AWS's own framework Chalice https://github.com/awslabs/chalice https://github.com/awslabs/chalice it basically has you import Chalice where you would otherwise import flask, making it fairly easy to switch to hosting yourself later if you want.

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).

kuschku 10y ago
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.
interactiv 10y ago
> 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 ...

psuter 10y ago

FWIW, OpenWhisk, while available on IBM Bluemix, is also open source and can be run wherever you so desire: https://github.com/openwhisk/openwhisk https://github.com/openwhisk/openwhisk

takeda 10y ago
If you want to run it in aws you will still have to run it on a server. BTW: I really hate the marketing inventions. There's no cloud, or serverless, you still run your software on someone's server.
- coredog64 10y ago
  I hear ya. The keyless entry on my Prius still requires me to carry a key.
  - takeda 10y ago
    That's a bit different, you have a different technology (although it still contains a key as a backup) and call it a key. Anyway the serverless is essentially (as someone here pointed out) the same idea as shared hosting which is very popular with php. It just uses a different name.

harryh 10y ago

Not if you build things in a thoughtful way. The code behind a REST call shouldn't really be all that different when deployed to Lambda vs run in a standalone binary on a rackspace server.

joecot 10y ago

There are a number of frameworks that should make migration between services pretty reasonable. Check out Serverless https://github.com/serverless/serverless https://github.com/serverless/serverless . It'll work for Lamba, google cloud, Azure, and IBM Whisk If you look at AWS's own framework Chalice https://github.com/awslabs/chalice https://github.com/awslabs/chalice it basically has you import Chalice where you would otherwise import flask, making it fairly easy to switch to hosting yourself later if you want.