[sharken]

Multi-cloud is a nice idea, but not for everyone.

Where i'm at it has been SQL Server for the last 12 years and now Azure for cloud services.

It's highly unlikely that will change for the next 10 years.

And almost equally unlikely that Terraform will be used instead of ARM templates and Bicep.

[urthor]

Cannot agree with this more.

Single cloud has a few extraordinary benefits for slow moving organizations.

Once you hang up the sign and declare "we are an xxx shop" it becomes an extraordinarily effective tool to drag unsophisticated employees and departments into the future.

"Microsoft said we have to do this so we have to" overcomes a LOT of internal barriers to technical change.

The biggest problems are never technology in large organizations, it's the humans beings anxiously protecting their overpaid managerial role. Single cloud is amazingly effective at improving the human factor.

At more sophisticated places with a bigger human appetite for innovation of course it's a different story.

[dragonwriter]

> "Microsoft said we have to do this so we have to" overcomes a LOT of internal barriers to technical change

“Microsoft said we have to do this so we have to” is a lot of internal barriers to technical change.

At least, that's what I see working in an public sector enterprise shop whose cloud transition started as involving a break from being a solid and conservative narrow Microsoft shop which is currently backsliding as that transition broadens and innovators at all levels (including the CTO that spearheaded it, who is departing for a CIO gig) move on or are marginalized.

[urthor]

I sympathize, but what is the obstacle standing in the way of "if it's on Azure why don't we just use it?"

That's often a moderately straightforward discussion.

[cyberpunk]

It makes very little sense. I mean, sure, maybe try to avoid vendor specific databases and use stuff like rds/managed cassandra/whatever vs Bigtable or dynamodb, but it's MUCH cheaper to lean in as hard as you can to one cloud provider and just pay for a month or three of consultants to move you if you ever actually want to than it is to build that in from the start.

k8s is a nice way to get there, if your k8s is running on gcp, aws, or azure it doesn't really impact your pipelines or process at all.

Things are harder at the bleeding edge, I'm working atm on a site that's all in on aws lambda with server less framework and aurora, kinesis and such, to the point where a migration would mean a rewrite tbh.. And that's alright for them, they're ok with their cloud partner.. And it's cheap too..

[thedougd]

It's not unrealistic to expect a stack that includes Azure, GitHub, Datadog, Okta, Pagerduty, and more for a single application. Terraform handles and ties them all together well with a single application focused configuration.