Cheat sheet · Specialise
Data engineering cheat sheet (Azure)
Opens with creditsFor students and early-career engineers learning data engineering on Azure, from the data lifecycle and analytical SQL to modelling, Spark, Airflow, dbt and streaming. Cloud snippets use ADLS Gen2, Event Hubs and Terraform on Azure, and the platform chapter maps each idea to Microsoft Fabric, Data Factory and Azure Databricks.
Chapters
10 chapters · 77 concepts
1Foundations and ingestionWhat data engineers do, the lifecycle every platform follows, the main pipeline patterns and how to pull data from sources safely.10 concepts
- 1Data engineerAn engineer who builds and runs the systems that collect data from sources, store it, transform it into reliable tables and serve it to analysts, data…
- 2Data engineering lifecycleThe stages data passes through: generation in source systems, ingestion, storage, transformation and serving, with security, quality, orchestration and cost…
- 3Batch and streamingBatch processes data in chunks on a schedule, such as yesterday's orders every night.
- 4ETL and ELTETL transforms data before loading it into the warehouse.
- 5Full and incremental loadsA full load copies the whole source table each run.
- 6Change data captureReading a database's own change log, such as the PostgreSQL write-ahead log or MySQL binlog, to capture every insert, update and delete in order.
- 7API ingestionPulling data from an HTTP API while handling pagination, rate limits (HTTP 429), authentication and retries with exponential backoff.
- 8Python for pipelinesPython written to run unattended: small functions, configuration from environment variables, logging, clear exceptions, pinned dependencies and a non-zero exit…
- 9DuckDBA small, in-process analytical database that runs SQL directly over CSV, JSON and Parquet files on your laptop, much faster than pandas on larger data.
- 10Idempotent pipelineA job that produces the same result whether it runs once or many times for the same input, for example by overwriting a date partition or using MERGE instead of…
10 in this chapterOpen this chapter2Analytical SQL and data modellingThe SQL patterns pipelines rely on and the dimensional modelling ideas that turn raw tables into a warehouse people can trust.12 concepts
- 1Common table expressionA named subquery defined with WITH at the start of a query, so a long transformation reads as a series of steps.
- 2Join fan-outWhen a join matches one row to several rows on the other side, multiplying rows and inflating sums.
- 3Window functionsFunctions that compute a value for each row from a related set of rows, defined with OVER (PARTITION BY ...
- 4DeduplicationKeeping one row per business key, usually the latest version, by numbering rows per key and keeping row 1.
- 5OLTP and OLAPOLTP systems run applications with many small reads and writes on normalised tables.
- 6Fact tableA table of events or measurements at a declared grain, holding foreign keys to dimensions and numeric measures such as quantity and amount.
- 7Dimension tableA table describing the context of facts: who, what, where and when, such as customer, product, store and date, with descriptive attributes.
- 8GrainExactly what one row of a fact table represents, stated in one sentence before any columns are chosen.
- 9Star and snowflake schemasA star schema has one fact table joined directly to denormalised dimension tables.
- 10Surrogate keyA meaningless key, an integer or a hash, created in the warehouse to identify a dimension row, separate from the source system's natural key.
- 11Slowly changing dimensionWays to handle dimension attributes that change.
- 12Kimball, Inmon and data vaultModelling styles: Kimball builds star schemas per business process; Inmon builds a normalised enterprise warehouse first; data vault splits data into hubs…
12 in this chapterOpen this chapter- File formats, lakes and lakehousesHow analytical data is laid out on disk and in object storage, and the difference between lakes, warehouses and lakehouses.11 conceptsOpens with credits
- Batch processing with SparkHow Apache Spark splits work across a cluster, the PySpark API, the few performance ideas that matter and how to write batch output safely.6 conceptsOpens with credits
- Orchestration with AirflowRunning pipeline steps in order, on schedule, with retries, backfills and alerts, using Apache Airflow as the example.6 conceptsOpens with credits
- Transformation with dbtBuilding warehouse models as tested, documented SQL with dbt: models, materialisations, tests, incremental models and snapshots.5 conceptsOpens with credits
- Your cloud data platformThe building blocks every cloud offers for data: object storage, a catalogue, a warehouse, managed Spark, access control, secrets and cost control.7 conceptsOpens with credits
- Streaming basicsEvent logs, Kafka's core ideas, delivery semantics, event time and windows, and the managed streaming service on your cloud.10 conceptsOpens with credits
- Data quality and governanceKeeping data trustworthy and safe: quality checks, contracts, observability, lineage and handling personal data.6 conceptsOpens with credits
- Infrastructure, CI and careerMaking pipelines repeatable with containers, Terraform and CI, and the cloud certifications that data engineering roles mention.4 conceptsOpens with credits
- 11Glossary, A to ZEvery concept in the sheet and the smaller terms it uses, in one list.197 terms
About this sheet
Pipelines, warehouses, Spark, dbt.
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allBest practices
See all- Data Pipeline Best PracticesHow to build data pipelines you can re-run, test and trust: idempotent tasks, orchestrator hygiene, layered transformations, data tests, freshness, ownership and monitoring.
- Data Analysis Best PracticesAn analyst's workflow in SQL, pandas and Polars: framing the question, reading data correctly, joins and grain, aggregation pitfalls, reproducible notebooks, checking results and sharing findings.
- Data Modeling Best PracticesDimensional data modeling for analytics: declaring the grain, fact and dimension tables, slowly changing dimensions, dbt marts, naming, tests, contracts and a semantic layer.
Checklists
See all- Data Quality ChecklistA data quality checklist for warehouse tables: ownership, freshness, volume, schema, nulls, uniqueness, referential checks, anomaly monitoring and data incidents, with how to verify each.
- Analytics Dashboard ChecklistAn analytics dashboard checklist for launch day: purpose and audience, metric definitions, data freshness, correctness, performance, access, accessibility, ownership and adoption.
- ML Model Deployment ChecklistAn ML model deployment checklist: baselines, training and serving consistency, validation, model registry, canary rollout, rollback, drift monitoring and ownership, with how to verify each.
Project structures
See all- dbt project project structureA dbt project that turns raw tables into tested, documented models, using the staging, intermediate and marts layers from dbt's own structure guide. It runs on DuckDB on your laptop, so you can learn analytics engineering for free, and grows into a governed project with checks, contracts, slim CI and a hosted docs site that moves to BigQuery or Snowflake unchanged.
- Apache Airflow project structureFor data engineers scheduling real pipelines with Airflow 3. It starts from
astro dev init(dags, include, plugins, tests and a Runtime Dockerfile that runs Airflow locally in Docker) and grows into dags grouped by business area, logic in a tested include package, asset-driven scheduling, data quality checks, alerts, CI that parses and tests every dag, and dag-only deploys. A self-hosted docker compose and Helm route is shown alongside. - GenAI RAG app (FastAPI) project structureFor developers turning a "chat with your documents" demo into an app people can rely on. A FastAPI backend where every layer has a home: ingestion workers, retrieval, prompts as versioned files, model clients with fallbacks and cost caps, guards, evals that gate CI, and tracing, so a wrong answer can be traced to the step that caused it.
Career questions
See all- What is the difference between a data analyst, a data scientist and a machine learning engineer?Analysts answer business questions with SQL, spreadsheets, dashboards and reports. Data scientists add statistics, experiments and predictive models. ML engineers build and run models inside production software. Titles vary by company, so read the work in the job advert, and pick by the kind of problem you enjoy, not the title that sounds most senior.
- How do I switch from data analyst to data engineer?You already have the hardest part: SQL, business context and knowing what good data looks like. Add Python for pipelines, data modelling, an orchestrator, a cloud warehouse, Git and testing. Build one end-to-end pipeline, then move internally by taking on engineering work in your current team before applying outside.
- Can I get a remote data engineering job from Africa?Yes, it is realistic, and data engineering is one of the skills global employers most often hire remotely from Africa. You need solid SQL and Python, one cloud platform, a pipeline tool and a warehouse, two or three end-to-end projects, and a search aimed at remote-friendly companies and talent platforms. Most remote hires have some experience, so a local first job helps.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com