Transformation Engines
Glue, EMR, and the Spark underneath both: where a Glue job beats a cluster and where it does not, DPUs and executors as the same idea priced differently, the file-size and partition problems that dominate real pipeline cost, and why a slow job is usually a shuffle rather than a CPU.
Content current as of 2026-10.
Lessons
- AWS Glue ETL and its job model
- Spark mechanics a data engineer must know
- EMR: when the cluster earns its keep
- File formats, compression, and partitioning
- Diagnosing a slow transformation
Sources
- AWS Glue developer guide — AWS Glue worker types
- AWS Glue developer guide — tracking processed data using job bookmarks
- AWS Glue developer guide — reading input files in larger groups
- Amazon EMR release guide — optimize Spark performance
- AWS prescriptive guidance — tuning AWS Glue for Apache Spark
- Amazon Athena pricing — worked examples