<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Databricks on Rework-Space</title><link>https://rework-space.com/blog_tags/databricks/</link><description>Recent content in Databricks on Rework-Space</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rework-space.com/blog_tags/databricks/index.xml" rel="self" type="application/rss+xml"/><item><title>Landing Zones as Code: A Terraform Blueprint for Azure Databricks and Pipelines-as-Code</title><link>https://rework-space.com/blog/2026-08-17-terraform-blueprint-azure-databricks-landing-zones/</link><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><guid>https://rework-space.com/blog/2026-08-17-terraform-blueprint-azure-databricks-landing-zones/</guid><description>The problem In Part 1 we built a FinOps pipeline on Azure Databricks that merges Azure infrastructure billing and Databricks DBU usage into one FOCUS-format cost lakehouse. It works. But if the workspace it runs in was assembled by clicking through the Azure portal, you own an environment nobody can review, reproduce, or roll back.
Portal-built platforms fail quietly. The network rule someone added during an incident is undocumented. The second workspace differs from the first in ways nobody can list.</description></item></channel></rss>