---
title: "Discussion on \"IAC Face-Off: Databricks Asset Bundles vs Terraform\" | Hashnode"
description: "Discussion on \"IAC Face-Off: Databricks Asset Bundles vs Terraform\". Data Engineers often have to juggle both data processing and DevOps pipelines. I’ve worked with many skilled data professionals, but they tend to shy away from the DevOps side of things. Often, I get asked to take over this aspect due to my backgroun..."
url: "https://hashnode.com/posts/iac-face-off-databricks-asset-bundles-vs-terraform/686a6868b11c4e85f3ecdd00"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [IAC Face-Off: Databricks Asset Bundles vs Terraform](https://data.kurdapyo.com/iac-face-off-databricks-asset-bundles-vs-terraform?utm_source=hashnode&utm_medium=feed)

Data Engineers often have to juggle both data processing and DevOps pipelines. I’ve worked with many skilled data professionals, but they tend to shy away from the DevOps side of things. Often, I get asked to take over this aspect due to my backgroun...

Jul 6, 2025 · 3 min read · data.kurdapyo.com  
Updated Jul 11, 2025  
Read the article

-   [#databricks](https://hashnode.com/tag/databricks)
-   [#databricks-asset-bundles](https://hashnode.com/tag/databricks-asset-bundles)

## Written by

[Kurdapyo Data Engineer](https://hashnode.com/@kuya)

@kuya · Sydney, Australia

  
[View profile](https://hashnode.com/@kuya)

A old database developer's take on data engineering, cloud and data SaaS products

I’m the kuya(older brother) at Kurdapyo Labs — an ex-Oracle developer who saw the light and helped migrate legacy systems out of Oracle (and saved my employers a lot of money doing it). I used to write PL/SQL, Perl, ksh, Bash, and all kinds of hand-crafted ETL. These days, I wrestle with PySpark, Airflow, Terraform, and YAML that refuses to cooperate. I’ve been around long enough to know when things were harder… and when they were actually better. This blog is where I write (and occasionally rant) about modern data tools — especially the ones marketed as “no-code” that promise simplicity, but still break in production anyway. Disclaimer: These are my thoughts—100% my own, not my employer’s, my client’s, or that one loud guy on tech Twitter. I’m just sharing what I’ve learned (and unlearned) along the way. No promises, no warranties—just real talk, some opinions, and the occasional coffee/beer-fueled rant. If something here helps you out, awesome! If you think I’ve missed something or want to share your own take, I’d love to hear from you. Let’s learn from each other.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
