3 ms·
This looks cool and I love the taxonomy and owning your own data. But I wonder if you are trying to do too much. For example, why would I use Bach to transform
by mjirv 4y ago
This looks cool and I love the taxonomy and owning your own data.
But I wonder if you are trying to do too much. For example, why would I use Bach to transform my data instead of just doing it in my dbt project or wherever else I handle warehouse transforms?
- thejansen 4y agoHi, thanks for diving in. Yes, this is a lot. Let me try to explain how we got here. Bach will abstract the transformations that make up the models away from the SQL dialect, making models built using Bach reusable on any SQL based data store (once all dialects are supported of course). This allows you to generate the required SQL for your enviroment using Bach, and running that through your DBT or other transformation setup on your warehouse. This, combined with a strict taxonomy, leads to (at least we hope) reusable models between different products/users, and data platform configurations. We've not seen a way to achieve this without doing all of the above.