2 ms·
> Multi-cloud is simple, just don't use anything that's unique to a particular provider. Using provider-specific services is fine. You only need to be mindful
by chipdart 2y ago
> Multi-cloud is simple, just don't use anything that's unique to a particular provider.
Using provider-specific services is fine. You only need to be mindful of what it will take to migrate that functionality out of that specific cloud provider,and what work will be required to replace it.
Everything is a tradeoff. The time and cost required to roll out a feature is balanced by the cost of avoiding a tie-in. It makes no sense to spend ages and tons of cash writing a cloud-agnostic implementation when a one-liner of a cloud-specific service does the same job.
- magicalhippo 2y agoWe're moving an on-prem Windows app to the cloud, and that's the approach I've taken so far when staking out our approach. We use Azure blob storage, but just the parts that reasonably maps to say S3. We're using Azure Service Bus, but keep to the AMPQ bits. We use Entra ID, but rely on OAuth and SCIM. And so on. So far we've not needed special functionality for anything critical, so while it wouldn't be just a flick of a button, the hope is we're avoiding painting ourselves in a cloud provider corner. Time will tell, hadn't done any cloudy stuff until a year or so ago.