3 ms·
>>> I wonder has anyone who actually goes through all of the lengths trying to “avoid vendor lock-in” actually sat down and done a realistic project plan of ho
by user5994461 6y ago
>>> I wonder has anyone who actually goes through all of the lengths trying to “avoid vendor lock-in” actually sat down and done a realistic project plan of how much it would cost as far as man hours and the amount of regression tests that would be required.
Did that for a web startup. Tens of services, 200 instances.
Estimated 1-2 weeks to move to another cloud provider (Google/Azure) and be back online for customers.
- scarface74 6y agoI also work for a startup. While we have fewer instances. We have a lot of data and any move would trigger audits for security and compliance. We would have to work with each of our customers (large businesses) and make sure they white list the new IP addresses (yes something as simple as depending on your vendor for an IP address can trigger lock-in). 100-200 VMs - especially if they are all based on the same few image is easy.
- user5994461 6y agoWe also have audits, compliance and security to take care of, and at least IP whitelisting around payment integrations. I am considering a disaster recovery scenario. Like AWS banned the account or all the resources were deleted. There is nothing to do but to start over from scratch, every single employee is onboard to help and get their bits of services back working. Audits is not a rebuild step, it's something to arrange much later.