This project is supporting the VBD ADB 360, which strives to be a 360 degree end to end solution of Azure Databricks implementing a lakehouse on a medallion architecture, supported by Unity Catalog. The end to end solution demonstrates the following concepts:
- CICD of Azure Databricks with infrastructure (IAC) as well as content
- Implementation of a Lakehouse on a medallion architecture
- Unity Catalog (UC)
- Delta Live Tables (DLT)
- Enterprise Logging
The Repository is structure into two main parts:
- IAC : Infrastructure as code in directory iac-adb-360
- Content : the notebooks and workflow definitions to implement the lakehouse with the medallion architecture
How to Proceed:
flowchart TD
Start --> IaC(Infrastructure as Code at iac-adb-360/readme)
style Start fill:red,stroke:blue,stroke-width:3px,shadow:shadow
IaC --> Content(Content and Data in content-adb-360/Readme)
style IaC fill:darkgray,stroke:blue,stroke-witdth:3px,shadow:shadow,color:#0000aa
Content --> End
style Content fill:darkgray,stroke:blue,stroke-witdth:3px,shadow:shadow,color:#0000aa
style End fill:red,stroke:blue,stroke-width:3px,shadow:shadow
- Other helpful links:
- Install Databricks CLI v 2.0 (> 0.205) GA as of March 14, 2024
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.