Why would I use DBT?

DBT, or Data Build Tool seems to get a lot of traction lately. Let's look at this thing together. How does it work, where would it fit in a data warehouse stack and of course, is this something you or I would use?

The Data Engineer space is on fire, and new tools and techniques are showing up at breakneck speed. Some of them seem to get more traction than others. DBT, or Data Build Tool, seems to be one of those highly popular tools. Backed by venture capital and coming almost out of nowhere, I heard about it more and more and I got curious. I've got some experience in the ETL world with old and new tech and big and small environments. Let's look at this thing together. How does it work, where would it fit in a data warehouse stack and of course, is this something you or I would use?

Speaker

André Kamman's Sessions

FinOps, how data engineers get their cloud cost under control

Generate test data quick, easy and lots of it with the Databricks Labs Data Generator

Keynote by The Community

D, E and I Panel

Building your first Metadata Driven Azure Data Factory

Looking under the hood of the parquet format

My top tips for continuous learning without spending every minute of your free time on it

Schema Madness, handling (incompatible) schema changes in incoming json files with Databricks

The stress of many options, which ETL and DWH engines do you combine and why?

Why would I use DBT?