4 ms·
I was handed a policy document at my previous job that said: "In the event <CEO of provider> spits at <CEO of ours>, we must be able to migrate in 2 billing cyc
by dijit 5y ago
I was handed a policy document at my previous job that said: "In the event <CEO of provider> spits at <CEO of ours>, we must be able to migrate in 2 billing cycles".
The reason isn't the spit, it's to prevent being so locked in that the provider can rent seek; but there's also an element of agility in that. If you can turn to AWS and say "Give us a good deal or we walk" and.. you know, you actually can walk... then they're more likely to do that.
This is the same reason broadband is fairly inexpensive in Sweden, the building will negotiate as a unit to an ISP and get a group deal. Bulk buying in this way gives a lot of negotiating power. So for a publisher to be able to move all titles to a new provider in 2 cycles: that's negotiation power.
If you can save 2 months of developer time in a year by switching providers, it behooves to do it; and cloud resources are _expensive_ I recently specced out an instance for gitlab which is currently living on a VPS, it went from $30 to nearly $800 on cloud. (Though admittedly that $800 variant would be more highly available.)
- xyzzyz 5y ago> The reason isn't the spit, it's to prevent being so locked in that the provider can rent seek; As a minor pedantry, your cloud provider cannot "rent seek" just because you stepped into a vendor lock-in situation, that's not what the phrase "rent seeking" means. An example of actual rent seeking would be if US government legally required you to use AWS if you were doing business in some highly regulated sector. Being locked in particular vendor offering is definitely not a great situation, and the vendor can most definitely use the leverage to their own profit, it's just this is not rent-seeking.
- bushbaba 5y agoI wish more businesses operated this way. Doesn’t mean you can’t use AWS Managed offerings of open api/source products (e.g. EKS, rds, s3). The strategy provides for healthy friction and drives customer obsession by the vendor.
- Aicy 5y agoI don't. In reality it can incredibly difficult and expensive to switch all your infrastructure over to a new cloud provider, and hybrid / multi cloud is expensive and complicated to design and operate.
- sangnoir 5y ago> multi cloud is expensive and complicated to design and operate. Depending on your scale, not being multi-cloud can be more expensive. i.e. You can save more money than it costs you to migrate (by getting a discount from your current provider.) When negotiating, you need to be able to walk away, for real.
- deleted 5y ago[deleted]
- bob1029 5y agoOne thing you can also do is try to script a rebuild of your entire infrastructure to such an extent that you can make total rebuilds from scratch a normal part of your operating procedures. Hypothetically, if you had 1 big script that could rebuild your entire org inside Azure/AWS within 4 hours, why wouldn't you consider doing this as a normal part of every weekend? If a meteor hits us-east-1, you wouldn't even have to think about it. It would just be another Saturday, perhaps with a quick region toggle in the redeploy script parameters. Other advantages with weekly orbital nukings of infra also includes making it very difficult for persistent threats to... persist. Clearly, some resources cannot be re-allocated with such frequency. Domain registrations and maybe TLS certs being the biggest examples. Getting away from needing static IP addresses in your cloud provider can also remove a lot of shackles.
- nunez 5y agoTwo billing cycles in two months. For a small company or a medium-sized company with "modern" apps and app deployment processes, then that's somewhere between a nothing-burger and an inconvenient weekend (during which the engineers would get paid OT, hopefully!). For large companies with >$100k/month spend in AWS and sizeable legacy application assets, that's a death-march.
- snotrockets 5y agoUnless that migration is constantly tested, it's not going to happen in two billing cycles. Cloud providers aren't Comcast. You don't get discounts for threatning to move from, because both providers and customers know the costs are impossibly high. Which is why a lot of their pitch is that never be in a situation where you'd have to do move (some of course are better here, one cloud is trying very hard to overcome their parent company reputation), otherwise no sane executive would sign up. The discounts you do get from clouds is by promising to move more work to them.