How databricks/tmm works
Project type and purpose
• At the top level, this is not a single application but a monorepo of multiple “Tech Marketing” training and demo projects. Each folder (e.g., Cookies-DataEng-DAB, DLT-Kafka-Sink, Genie-Speak, GenAI-Workshop, Lakeflow-DataEng-Workshop, etc.) is a standalone workshop or demo illustrating data-engineering pipelines, ML/GenAI workflows, API services, or ETL patterns on platforms like Databricks, Kafka, Flask, etc.
• The README confirms that these are “examples…for training and tech demos,” with no single cohesive runtime but a catalog of reference implementations.
File structure
• Top-level directories ≈ individual demo/workshop modules.
• Common file types per module:
• .py and .ipynb (Python scripts and notebooks) for logic and interactive demos
• .sql, .dbquery, .yml (ETL pipeline definitions, SQL transforms, orchestration configs)
• JSON/YAML dashboards and config templates (e.g., Databricks, Kafka, aibi dashboards)
• resources or misc folders for sample data, schemas, or ancillary scripts
• Cross-cutting files/folders:
• sample_data for seeds
• shared license, .gitignore
• No single build script—each module is self-contained.
README for additional insights
• Confirms monorepo of “as-is examples,” no enforced architecture described.
Final advice
• Be exhaustive: represent each folder as a component group, then drill into its main scripts, configs, and data flows.
• Medallion pattern in ETL demos and service pipelines in API demos.