cloud:aws:big_data:glue
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| cloud:aws:big_data:glue [2023/10/19 06:48] – skipidar | cloud:aws:big_data:glue [2023/11/01 07:13] (current) – ↷ Page moved from business_process_management:camunda:cloud:aws:big_data:glue to cloud:aws:big_data:glue skipidar | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| + | ===Summary: | ||
| In summary, **AWS Glue is a more suitable** choice when you want a **fully managed**, serverless ETL service with a focus on simplifying data preparation and transformation, | In summary, **AWS Glue is a more suitable** choice when you want a **fully managed**, serverless ETL service with a focus on simplifying data preparation and transformation, | ||
| AWS **EMR, on the other hand**, is **ideal for highly customized, complex big data processing tasks** that require a **high degree of control and support for various big data frameworks**. The choice between them depends on your specific use case and requirements. | AWS **EMR, on the other hand**, is **ideal for highly customized, complex big data processing tasks** that require a **high degree of control and support for various big data frameworks**. The choice between them depends on your specific use case and requirements. | ||
cloud/aws/big_data/glue.1697698135.txt.gz · Last modified: by skipidar