amazeeio / docs

Documentation of legacy hosting environment

Home Page:https://docs.amazee.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cloud Vendor Agnostic

kirkilj opened this issue · comments

It might be useful to indicate on the comparison matrix the work that would be required if someone wanted to move their Drupal site off of Amazee.io's platform compared to the other vendors. Upper management wants some assurances that we're not going to be locked-in and that migration to another platform will be relatively easier. A lot could be inferred from the use of Docker, but non-technical managers won't be able to make this leap without a translator in the room.

@kirkily

Thanks for your very good question! On side of amazee.io we made sure from the beginning, that it is easily possible to move away from us. As we don't provide or require our own git hosting, moving away is super easy: Just remove access from your git repository from us and it's done :) Plus you also have access to all backups, all files, etc.

Unfortunately we don't exactly know how that is with our competitors, but the fact that they require their clients to migrate to another git repo makes it harder.

We will definitely add a new line to the comparison :)

Thanks for the quick response Michael. I know that a "no vendor lock-in" capability is listed as a competitive advantage for several Internet services. Being able to move your Drupal docker installation onto customer premises is a related differentiator for some of the large companies that are interested in being an enterprise beta tester of our startup a year or three down the road. I'm not sure an entry in the comparison will be sufficient to paint a compelling picture of the ease of migrating to other hardware, PaaS environments, either to another cloud provider or on customer premises. A Migration article might be a better resource with recipes for each scenario you care to document.

closing due to inactivity