#71: The Missing Piece In Many Data Pipelines
Jul 03, 2024All data teams (large & small) have at least one thing in common.
Source data.
But not everyone handles it the same way in their pipelines.
For some, they'll reference raw source tables directly in many queries.
For others, they'll create ad-hoc custom tables to address subtle formatting changes.
But without any real over arching strategy or consistent naming behind it.
While a more popular topic is data modeling (ex. kimball, one big table, etc.)
I believe an equally more important area to consider is what you do BEFORE you start creating those core data models.
For many, this "before" layer doesn't exist at all.
In previous videos I've talked about a 3-Layered Data Model.
And today I want to focus solely on Layer 1, which addresses this concept.
It's called a "Staging" layer.
When done right, it can help you establish reliable pipelines from the very start.
The main things we'll cover include:
- The purpose of a Staging layer
- A simple naming convention to follow
- How it can make your data pipelines more clear & consistent
Enjoy!
Michael
When you're ready, here are 2 other ways I can help you:
1. Simple Stack Academy: Level-up your data career by learning more than just SQL. Design, build & automate an end-to-end data architecture using modern tools like dbt⢠& Github. (Free 7 Day Preview)
2. Consulting Services: Get personalized support to properly implement a well-structured, scalable, and maintainable data architecture at your company.