Scalable mono repo data engineering workloads #44
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.
This is an "in-depth" example of a scalable, modularised repo structure for all Data Engineering workloads using DABs. It supports the following:
The aim of this example is not to define a de-facto approach for DABs projects but to give companies / individuals an example as to how they might structure all of their Databricks application code in a single mono-repo.
All additional fixtures such as Makefiles, workflows, pre-commit hooks, etc. are entirely optional & can be removed if needed.
All in-line comments & README instructions can be altered so please let me know if anything has been missed / is too specific / doesn't make sense.