3 ms·
My 2¢ is "most companies should not avoid vendor lock-in, but rather should lean in and make maximum productive use of the tools and features that their chosen
by sokoloff 4y ago
My 2¢ is "most companies should not avoid vendor lock-in, but rather should lean in and make maximum productive use of the tools and features that their chosen cloud vendor provides". Engineer time and attention is more expensive than most people give it credit for and designing for a future, seamless cross-cloud migration is building a gold-plated pyramid of YAGNI for most companies.
- glutamate 4y agoAre you talking about large or small companies? If small, why not just use RoR/Django/whatever + PostgreSQL? If large, then cloud costs absolutely matter. It seems that there is very small intersection where you need cloud scale but engineer costs exceed infrastructure cost.
- sokoloff 4y agoI think small and medium is well suited for cloud in areas where engineers are scarce or expensive. For me, cloud is more about pace, flexibility, and engineering efficiency than it is about scale. Even my little side projects I run on cloud. I don’t want to futz around learning how to configure, secure, and scale a DB server if I can order one up or use DynamoDB. I agree that very large and hyper scale companies are a worse fit for the cloud, largely in part because they can afford to dedicate centralized teams to running great ops. Tiny, small, and medium can’t.
- jerrygenser 4y agoAgree mostly, however if you are a early-mid stage startup gaining traction and have enough of an engineering understanding to not become too coupled, then you can basically play the vendors against each other and get startup discounts or other types of discounts by swapping. I've heard of cases where vendor A gives a big discount to the tune of a the most recent year of annual billing from vendor B if you can prove that you most recent bill from vendor B is 0 due to completing the migration.
- Terretta 4y agoYes, and ... Pre-plan your offramps in case of necessary migration, architect and document those plans, and maintain those plans in the documentation of each service, so you keep those off ramps in mind as the service evolves.
- azemetre 4y agoHow does this account for the engineering time, attention, and effort it takes to use these cloud services? A common sentiment you hear online is that if you're on prem you need to hire specialist to management this software while neglecting the same is still true if you use a cloud provider. You'll still need to hire and train staff that are experts in AWS (or whatever cloud provider you use). If you're just deploying with containers then I suppose all is good, but isn't the risk still there?
- sokoloff 4y agoI think it outsources a slice of that effort (rack, stack, cool, basic networking) for all the AWS services and a lot of the server administration when you choose managed services. It does not eliminate all learning curve, but the learning curve to get a static site hosted on S3/Cloudfront is a lot lower than the learning curve to do the same on prem starting from bare metal.
- spiffytech 4y agoI agree with this in principle, however it seems proprietary cloud services often make development workflows more complicated, offsetting their operational simplicity and cost savings. That makes it harder to tell what the right call is in any given situation.