# How we (used to) structure our dbt projects

**URL:** <https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355>\
**Category:** Archive\
**Created:** [May 10, 2019, 6:57pm UTC](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355 "2019-05-10T18:57:22Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![claire](https://sea2.discourse-cdn.com/flex020/user_avatar/discourse.getdbt.com/claire/32/522_2.png) [@claire](https://discourse.getdbt.com/u/claire)\
**Post date:** [September 21, 2020, 8:11pm UTC](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355/19 "2020-09-21T20:11:56Z")

</div>

Check out this post:

> [@books DW Design: which books should I read in 2020?](https://discourse.getdbt.com/t/dw-design-which-books-should-i-read-in-2020/1129):
>
> On a related note [to this discourse post](https://discourse.getdbt.com/t/data-modeling-approaches-in-modern-data-times/1128), I’m interested to hear what resources people recommend for developing a strong theoretical grounding in DW design. I’m after a book or a few long and in-depth blog posts to explain the pros and cons of different models so that I can then make informed decisions given a particular use case. I’ve previously enjoyed Martin Fowler’s lengthy posts on software architecture, but he hasn’t done much on data architecture (and [what is there](https://martinfowler.com/articles/data-monolith-to-mesh.html) is laden with buzzword…

---

_[View the full topic](https://discourse.getdbt.com/t/how-we-used-to-structure-our-dbt-projects/355)._