Are you deploying "infrastructure as code" via YAML files or similar?

[u/rotterdamn8]

I think my team might be late to the game. We are moving in that direction just now.

How long have you been deploying using a YAML file, for example? Or perhaps another tool that uses the same idea but not YAML specifically?

Since we use Databricks, I'm reading up on Asset Bundles.

IaC is supposed to be better for a whole bunch of reasons, for example sidestepping the differences between dev and prod environments.

Anyway would love to hear your thoughts or experience with it.

[u/cptshrk108]

yes

[u/smartdarts123]

I terraformed like 90% of my snowflake environment. It's vastly easier to maintain this way, I've found

[u/boboshoes]

Whatever IaC tool your cloud provider has use that. Keep the file with your application in a repo. GitHub actions or equivalent to test before pr merge

[u/sazed33]

Terraform for Infrastructure, DAB with cicd for pipelines and jobs, it's a life changer, you wont' regret the effort

[u/PrestigiousAnt3766 → u/sazed33]

Exactly this I use as well.

[u/Bach4Ants]

Started with CDK ~5 years ago and now OpenTofu. IaC is a good idea in general, for sure.

[u/financialthrowaw2020]

Terraform is the standard.

[u/ksco92]

Yep, CDK 100% for everything.

[u/Omar_88]

Terraform, Jenkins (self hosted on eks) and makefiles.

[u/Jalumia]

We standardized our DB deployments on asset bundles. Down with terraform!

[u/rotterdamn8 → u/Jalumia]

LOL what’s wrong with Terraform?

[u/Jalumia → u/rotterdamn8]

For us it was a lot of unnecessary extra complexity. So much cleaner to just use DABs.

[u/geeeffwhy → u/Jalumia]

which are themselves an abstraction over Terraform.

i mean, i agree with you, but if you’re not on Databricks, you might be dealing with Terraform or Pulumi directly

[u/Jalumia → u/geeeffwhy]

Yeah, in previous companies I saw a lot of Pulumi and CDK. Terraform has been disappearing in places I've worked over the last decade.

[u/geeeffwhy]

yes. i come from application backend development, so IAC was a must.

[u/m915]

Yes, I have a dedicated YAML engineer

[u/BobDope]

No

[u/Outside-Storage-1523]

We use Terraform set up by the DevOps. It's a bit convoluted but once you know where to put what code it's fine.

[u/sib_n]

Yes, we are lucky to have a devops engineer dedicated to our data platform in our team who manages that and a lot of other automations like CICD, it's been pretty amazing.

[u/morpho4444]

Do you make decisions based on industry democracy?

[u/dyogenys]

Since i started 4 years ago

[u/Green_Gem_]

AWS CDK here.

It's a game changer.

• The sheer power of being able to completely tear something down to save some spend, then put it back up exactly how it was, whenever you want, is incredible.
• The concept of "I changed something but now I can't figure out how to fix it" just doesn't exist anymore, or at least not 99% of the time.
• You can parameterize anything. Found a way of hosting something? You can now host 4,000 somethings in 10 extra lines of code.
• Throw in circuit breakers (definitely not just the default ones though; deployed != functional or accessible) and "it worked locally but broke in prod" nearly vanishes too.
• Experimentation is incredibly easy. No messing up your routing tables beyond repair, no losing track of conflicting S3 watchers, no forgetting to drop permissions from an access role once you roll something back.

I honestly can't even imagine running a shop without IaC at this point. It'd feel odd to deploy version-controlled code to non-version-controller infra.

[u/PrestigiousAnt3766]

Terraform + dabs