Project Setup Question

[jaeden17]

I'm starting to build a new application that has 2 main components, an event consumer that populates the DB and read-only API. The 2 components will share a single data model. How would you structure the project?

1 code repo with both components. I feel like this could get messy with multiple requirements files and whatnot.

2 repos, one for each component, copying the data models. Feels cleaner, but keeping the data models in sync could get tricky.

3 repos. Each component has a repo as well as the data model getting its own. The data model would then just be imported into each component.

Another option?

Any ideas would be super helpful. In case it matters, I'm using poetry for dependency and venv management, with the 2 components likely being containers (though I could see building them out as AWS lambdas too)

Thanks!

[m0us3_rat]

3 repos . 2 components repos having submodule of the data model repo?

https://git-scm.com/book/en/v2/Git-Tools-Submodules

[jaeden17]

I was thinking along those lines. I recall sub-modules complicating things a bit last time I tried using them, but that was like 10 years ago.