Repository structures
Repository structure is a seemingly trivial but deeply impactful decision in any project. Take your time to think about how your team currently works, what types of operational patterns you wish to support, and how your teams will interact with the structure before deciding. Remember – you can always change your mind!
Mono-repo
A monolithic repo is a repository pattern where all of the code bases are placed in a single repository and tracked (and released) under a single version history. For example, you might have separate folders that contain your Airflow build system, separate folders for in-house operators/plugins, and a folder for each team that is publishing and distributing DAGs.
The mono-repo pattern is very powerful when you’re adopting a “working at the head” strategy. Even with multiple teams, it is very easy for all teams to have easy and direct access to all of the code required to make sure their DAGs run –...
