Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Why Glue: Serverless ETL on AWSâno cluster management; pay per DPU. Architectural logic: (1) Data Catalogâmetadata; table definitions. (2) Crawlersâdiscover schema; populate catalog. (3) ETL JobsâSpark or Python; transform. (4) Workflowsâorchestrate jobs and crawlers. (5)...
Red Flag: 'Glue is like EMR'âdifferent use cases. Pro-Move: 'Glue for serverless; we use Crawlers sparingly (cost)âschema in code for prod; Catalog for discovery.'
Why Glue: Serverless ETL on AWSâno cluster management; pay per DPU. Architectural logic: (1) Data Catalogâmetadata; table definitions. (2) Crawlersâdiscover schema; populate catalog. (3) ETL JobsâSpark or Python; transform. (4) Workflowsâorchestrate jobs and crawlers. (5) DataBrewâvisual prep. (6) Schema Registryâstreaming schema evolution. (7) Interactive Sessionsânotebook dev. Scalability: Serverless; auto-scales. Cost: DPU hours; crawlers and jobs separate. Trade-offs: Less control than EMR; cold start. When: Serverless preference; lake-centric; diverse sources.
Red Flag: 'Glue is like EMR'âdifferent use cases. Pro-Move: 'Glue for serverless; we use Crawlers sparingly (cost)âschema in code for prod; Catalog for discovery.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.