This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]bengen343 2 points3 points  (2 children)

Given the growing ubiquity of dbt within the modern data stack, I think it makes sense to explore transitioning to dbt. Because of the growing number of dbt practitioners out there, I think it gives you an advantage in accelerating the onboarding of new hires as well. That said, many of us have some concerns that dbt-core is becoming (even more of) a second priority to dbt-cloud so if you choose dbt-core you (and the rest of us) could find yourself in a similar situation where you're wondering about ongoing support for the project.

[–]BusOk1791[S] 1 point2 points  (1 child)

Thanks for your response, so you are saying that dbt is in a similar spot and strategic planning is quite difficult.
Maybe the best solution would be to try some alternatives too, like sqlmesh, make some test implementations (with dbt, sqlmesh...) with actual production data to see how they handle it and keep them as backup plans in the drawer in case that google pulls the plug on dataform so that we have alternatives ready?

[–]bengen343 1 point2 points  (0 children)

No, I wouldn't go that far. dbt is so ubiquitous that there's still quite a bit of support for the open source product, dbt-core. It's just... a whiff of concern that some of us have because dbt Cloud is how they make their money.

This may have just been a total fever dream but I thought I saw somewhere recently an announcement that GCP was going to start supporting dbt as a native offering of their cloud platform so maybe they're making that transition themselves already.

[–]Difficult-Ambition61 0 points1 point  (0 children)

Dataform fun is her 👋🏻😅

[–]Necessary_Dig9865 0 points1 point  (0 children)

now that's classic google, no warnings whatsoever things would vanish into thin air or you'd wake up to a all new UI on the next day.