3 ms·

Multi-cloud is simple, just don't use anything that's unique to a particular provider. (Losing weight is simple, just eat fewer calories than you burn.)

gchamonlive 2y ago
Simple but inconvenient. And it doesn't take much to get sucked into cloud lock-in. As soon as you need to work on permissioning that is slightly less trivial you start to sink.
- j45 2y ago
  Could permissioning not be run along the packaging to keep things cloud agnostic? Some days I wish there was an entire HN devoted to self-hosting and cloud-agnosticity lol.
  - fragmede 2y ago
    the problem is there's not an exact 1:1 mapping between clouds, so there's complexity to hold in your head. gcp project, aws account, and azure subscription don't represent exactly the same thing, so at some level you can paper over the differences but you really can't, once you get into the nitty gritty of it, so then you're left building up expertise as a multi-cloud software engineer that knows those subtle differences.
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 ago
  We'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.
deleted 2y ago
[deleted]

gchamonlive 2y ago

Simple but inconvenient. And it doesn't take much to get sucked into cloud lock-in. As soon as you need to work on permissioning that is slightly less trivial you start to sink.

j45 2y ago
Could permissioning not be run along the packaging to keep things cloud agnostic? Some days I wish there was an entire HN devoted to self-hosting and cloud-agnosticity lol.
- fragmede 2y ago
  the problem is there's not an exact 1:1 mapping between clouds, so there's complexity to hold in your head. gcp project, aws account, and azure subscription don't represent exactly the same thing, so at some level you can paper over the differences but you really can't, once you get into the nitty gritty of it, so then you're left building up expertise as a multi-cloud software engineer that knows those subtle differences.

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 ago
We'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.

deleted 2y ago

[deleted]