Data Engineering Community (DEC) (@data_dec) header
Data Engineering Community (DEC) (@data_dec) profile picture

A non-profit organisation providing Data Engineers a supportive and collaborative platform.

Nigeria
Joined April 2024
Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)Photo by Data Engineering Community (DEC) (@data_dec)
CI/CD for Airflow Pipelines Your Airflow DAG is code. So treat it like code. 📌Instead of changing production DAGs manually, you can have a workflow like: Code ↓ Git ↓ Pull Request ↓ Tests ↓ Review ↓ Merge ↓ Deploy
1
1
8
214
“I can maintain Airflow pipelines in a real engineering environment.” CI/CD is part of the second skill. 📌If another engineer had to maintain your DAG tomorrow, would they know how it's tested and deployed?
1
8
📌Resource of the Week: Astronomer — Airflow CI/CD and Testing Resources
8
Data Engineering Community (DEC) retweeted
This sounds like a simple question. But there is a trap. The interviewer already knows you know what these two are. That is not what they are testing. They want to know if you understand the architecture behind each one. Here🧵
2
4
4
111
Scheduling Is More Than @daily 📌One of the easiest things to do in Airflow is schedule a DAG: >>> schedule="@daily" But production scheduling is more complicated than that.
2
1
6
188
◉ Concurrency needs to be managed 📌Why it matters for data engineers A schedule tells your pipeline when to start. It doesn't automatically tell you whether the data is ready or whether another run is already in progress. 📌Take one of your pipelines and ask:
1
6
What happens if the source data arrives two hours late? 📌Resource of the Week: Apache Airflow Documentation — Scheduling
4
Retries Are Not a Magic Fix Your pipeline fails. Airflow says: >>> Retrying... Great. But should every failure be retried? Consider an API timeout. That's potentially a temporary problem, so retrying could make sense. Now consider invalid SQL.
2
2
121
◉ Tasks should ideally be safe to rerun ◉ Idempotency is an important part of reliable pipelines 📌Why it matters for data engineers A reliable pipeline isn't one that simply retries everything. It's one that fails safely and recovers predictably.
1
7
📌Ask yourself: If this task runs twice, will my data still be correct? 📌Resource of the Week: Apache Airflow Documentation — Tasks and Retries
6