3 ms·
Well I'd have to change my Terraform provider and the managed Kubernetes resource... Other than that, it'd be the same. So half an hour of coding + half an hour
by throwaway50182 3y ago
Well I'd have to change my Terraform provider and the managed Kubernetes resource... Other than that, it'd be the same. So half an hour of coding + half an hour of reconfiguring CI secrets?
- adam_arthur 3y agoPretty obvious to most that switching cloud providers is not quick or painless for the majority of orgs. There's not really an argument in good faith to suggest otherwise. Especially given that many orgs use managed or cloud specific solutions that have no 1:1 mapping between vendors
- throwaway50182 3y agoI said I'd have to change that one managed resource. Actually it's two - the managed database. But no more.
- atmosx 3y ago> I said I'd have to change that one managed resource. Actually it's two - the managed database. But no more. As someone who worked on a similar project recently, I'm getting that idea that you obviously don't know what you're talking about.
- motoxpro 3y agoDidn't you know? It's only one DB ENV variable and you're swapped over from GCP to AWS. /s
- throwaway50182 3y agoI'm running the tech for a global startup with 100M EUR turnover. It's still pretty small, but it's something. You need to plan ahead, sure. Portability was one of my main concerns (including the possibility to go self-hosted). But it's definitely not impossible, nor too hard to do.
- altdataseller 3y agoYou lost me at Terraform and Kubernetes..
- throwaway50182 3y agoWhat's a serious cloud provider-portable replacement for Terraform? And Kubernetes? It goes way beyond containers, you can replace many cloud provider-specific resources with Kubernetes resources. What alternative gives you that?