ETL Workflow Orchestration Step functions and/or Glue Workflows??
0
IHAC who's doing a low level design on their data lake. they want to use all AWS native services where possible. they have a question on ETL orchestration best practices on AWS. They were looking at Step functions but since Glue Workflow is available since Jun 2019 they were wondering which to use or a combo. Of course they are looking for the easy button. here's their primary requirements.
- ETL orchestration - step functions vs. Glue Workflow
- ~150 sources all sending files various times
- Source systems have limits on concurrency that scheduling tool must support
- example max 10 concurrent jobs for ACME source - job scheduling tool should pole and submit jobs keeping 10 active jobs but no more than 10
- ETL jobs should be built off of parameterized template where they pass in parameters like source, table name date and the job auto builds vs. having to maintain library of jobs/scripts per source/table. want this to be dynamically built
- Alerts on ETL processing
- Cloudwatch alert to SNS topics to etl teams on failures
- Cloudwatch alert to SNS for business users(loads complete)
- etc
- Support downstream jobs/etl example load file A & Load file B once completed for the day should launch load file C etc
Lingua
English
posta 5 anni fa3182 visualizzazioni
1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hey Dave,
It sounds like a perfect use case for Glue especially because the quantities and the concurrency is not too masive.
- Glue job accepts input values at runtime as parameters to be passed into the job. Parameters can be reliably passed into ETL script using AWS Glue’s getResolvedOptionsfunction.
- You can limit the number of running jobs by using the Data Processing Units (DPU) so it will run the number of jobs you need.
- For orchastrating more complex ETL graphs you can check out this documentation, it has a way of architecting it in a similar form of what you described in 6 ( https://docs.aws.amazon.com/glue/latest/dg/orchestrate-using-workflows.html ). In adittion you can concatinate job triggers and cloudwatch notifications like the following example: https://aws.amazon.com/premiumsupport/knowledge-center/start-glue-job-run-end/
Good luck! Ido
con risposta 5 anni fa
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Hi Dave, Thank you for your response. I still have some doubts regarding the parameters you mentioned in the first point, and I believe you can assist me with that. Currently, I am using a Glue Workflow to process my data, which is triggered by an Event using EventBridge. This workflow starts with a Glue Job that fetches the last file uploaded to the S3 bucket being monitored, which triggers the event. However, I'm unsure how to adapt my Glue Job to get the exact file that triggered the workflow. I am concerned about how the workflow will handle multiple files being uploaded simultaneously.