3 ms·
The choice of running in prem, or even changing cloud vendor is diminishing. Yes if you only use compute and storage moving is easy. If you want scaling in AW
by ThinkBeat 5y ago
The choice of running in prem, or even changing cloud vendor is diminishing.
Yes if you only use compute and storage moving is easy.
If you want scaling in AWS then move to Azure I think that would involve a lot of changes (as it would the other way) I am not sure how much of it Terraform can translate.
I would guess K8 can do this is a vendor neutral way but I am not sure since I have never worked with it.
I do know for a fact that getting your devops pipeline set up in AWS
is really complicated. We ended up having to hire two "elite" AWS
consultants for 14 days to get it all working.
I was not involved directly in it, but my team had great need of the finished pipeline. If we went with Azure we would have to do it all over again.
But most of our stuff is in .Net so getting it all working o Azure would have been magnitudes better.
The more "premium"/ high level services one starts using the ability to move on prem
or switch cloud becomes harder and harder. Which is of course the goal for the cloud vendors.
- pc86 5y agoSpeaking from experience, just because Azure is Microsoft doesn't mean that it's point-and-click to get a .NET app running on Azure, especially if you do anything non-standard in startup. Just google "ANCM in-process failure" to see dozens - hundreds - of out-of-the-box .NET apps that just refuse to run in an out-of-box Azure compute/VM.
- ThinkBeat 5y agoI agree. I have been in companies doing both. It is my experience that it is a lot easier on Azure than AWS. (At least as AWS was 2 years ago and Azure one year ago).
- AtNightWeCode 5y agoTo develop a canonical model over the infrastructure that can be reused between cloud providers takes a lot of knowledge. My experience from Terraform and Azure is that it is not in general worth it.