Re:Docker Releases Plugin for Simplified Deployments into AWS
by scarface74 on Monday July 27, 2020 @12:08PM
(#23966422)
When your build gets to be “millions per month”, you are already locked in. Any migrations is going to be a painful multi year progress. “Infrastructure has weight”.
Have you been part of an integration with a health care system? They are so tightly locked in to their existing EMR/EHR system it would make you cry. Every third party vendor that comes along has to integrate with it.
Part of the work I did at the company that I mentioned where I was a dev lead involved migrating our company from Workday. Their entire process was integrated into it.
Re:Docker Releases Plugin for Simplified Deployments into AWS
by jcims on Monday July 27, 2020 @01:59PM
(#23967664)
You're definitely locked in at some level, but if you are able and even demonstrate the ability to swing 30% of your workload over to another provider in a quarter, you're going to maintain some leverage.
Yes, have worked in healthcare on and off over the past 20 years and know precisely of what you speak. That's a different situation IMHO, same with ERP/HR/etc.
In addition, when your bills get to millions per month, the provider supplies quite a bit of TAMs and technical resources to your account. This can be helpful, but they also get a good understanding of where you are and are not in a position to dip out if things get sideways in billing. (Also, other providers will throw 6-7 figure credits your way to earn your business, being in a position to leverage them is a good thing.)
>Many intricacies like this are annoying, but at the same time advantageous if you know and use them.
This is very true. Building services or features that depend upon these is a good idea. Enshrining them deep within your assumptions and requirements about how you operate cloud-based workloads can work against you.