Introduction to IaC and Data Loading

Infrastructure as Code Concepts

Azure Bicep

Data Loading Tools (Fivetran/Airbyte)

Airbyte Cloud Lab

Practice

Assignment

Gotchas & Pitfalls

Week 14 Lesson Plan (Teachers)

Infrastructure as Code Concepts

Content coming soon...

Suggested Topics

• What is Infrastructure as Code: managing servers, databases, and networks through declarative config files
• Declarative vs imperative: describing the desired state vs scripting each step
• Benefits: reproducibility, version control, peer review, disaster recovery
• Azure Bicep: Azure-native IaC language, compiles to ARM templates
• IaC tools landscape: Azure Bicep, Terraform, Pulumi, AWS CloudFormation
• Bicep vs Terraform vs ARM templates: trade-offs (Bicep is Azure-only but simpler; Terraform is multi-cloud but requires state management)
• State management: tracking what resources exist and detecting drift
• Environments: using IaC to create identical dev, staging, and production setups
• Optional/advanced: Immutable infrastructure — replacing resources instead of modifying them in place
• IaC in the data world: provisioning databases, storage accounts, Airflow instances, and networking

The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0

*https://hackyourfuture.net/*

Found a mistake or have a suggestion? Let us know in the feedback form.