Updated project splitting section #6043
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
website/docs/best-practices/how-we-structure/5-the-rest-of-the-project.md
Outdated
Show resolved
Hide resolved
|
|
||
| - ❌ **Business groups or departments.** Conceptual separations within the project are not a good reason to split up your project. Splitting up, for instance, marketing and finance modeling into separate projects will not only add unnecessary complexity but destroy the unifying effect of collaborating across your organization on cohesive definitions and business logic. | ||
| - ✅ **Business groups or departments.** Conceptual separations within the project are a good reason to split up your project. For more information about dbt mesh, please refer to our [dbt Mesh FAQs](/best-practices/how-we-mesh/mesh-5-faqs). | ||
| - ❌ **ML vs Reporting use cases.** Similarly to the point above, splitting a project up based on different use cases, particularly more standard BI versus ML features, is a common idea. We tend to discourage it for the time being. As with the previous point, a foundational goal of implementing dbt is to create a single source of truth in your organization. The features you’re providing to your data science teams should be coming from the same marts and metrics that serve reports on executive dashboards. |
There was a problem hiding this comment.
Might make sense to move this one to the bottom so we get the ✅ s then one ❌
mirnawong1
reviewed
Sep 10, 2024
website/docs/best-practices/how-we-structure/5-the-rest-of-the-project.md
Outdated
Show resolved
Hide resolved
mirnawong1
approved these changes
Sep 10, 2024
There was a problem hiding this comment.
hey @nataliefiann , looks good to me but have a few suggestions. also heads up to remember to add a description in the pr and also add the the ‘Resolves #5424’ in the pr description too in order to close the open issue Beth raised
…-project.md Co-authored-by: dave-connors-3 <[email protected]>
…-project.md Co-authored-by: Mirna Wong <[email protected]>
…s/docs.getdbt.com into nfiann-project-splitting
nataliefiann
commented
Sep 10, 2024
website/docs/best-practices/how-we-structure/5-the-rest-of-the-project.md
Outdated
Show resolved
Hide resolved
|
Resolves #5424 |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What are you changing in this pull request and why?
Checklist
Following slack threadstarted by Jerco (https://dbt-labs.slack.com/archives/C02NCQ9483C/p1725973114198939) I've updated the project splitting section of the doc The rest of the project to show project splitting is supported with dbt Mesh
Resolves #5424