Skip to content

AWS Glue

  • AWS Glue is a fully-managed ETL (extract, transform, and load) service that makes it simple and cost-effective to categorize your data, clean it, enrich it, and move it reliably between various data stores and data streams.
  • AWS Glue consists of a central metadata repository known as the Glue Data Catalog, an ETL engine that automatically generates Python or Scala code, and a flexible scheduler that handles dependency resolution, job monitoring, and retries.
  • AWS Glue is serverless, so thereโ€™s no infrastructure to set up or manage.

How it works

  • AWS Glue is designed to work with semi-structured data.
  • It introduces a component called a dynamic frame, which you can use in your ETL scripts.
  • A dynamic frame is similar to an Apache Spark dataframe, which is a data abstraction used to organize data into rows and columns, except that each record is self-describing so no schema is required initially.
  • With dynamic frames, you get schema flexibility and a set of advanced transformations specifically designed for dynamic frames.
  • You can convert between dynamic frames and Spark dataframes, so that you can take advantage of both AWS Glue and Spark transformations to do the kinds of analysis that you want.

Use cases

  • You can use the AWS Glue console to discover data, transform it, and make it available for search and querying. The console calls the underlying services to orchestrate the work required to transform your data.
  • You can also use the AWS Glue API operations to interface with AWS Glue services. Edit, debug, and test your Python or Scala Apache Spark ETL code using a familiar development environment.

Reference architecture for streaming data pipeline

Reference architecture for streaming data pipeline

  1. Data Sourceโ€” In the previous architecture, there are multiple data sources. Near real-time data is generated through streaming data sources such as IoT devices, log and diagnostic data from application servers, and change data capture (CDC) from transactional data stores.
  2. Data steaming โ€” Messages and events are streamed into streaming services such as Amazon Kinesis Data Streams or Amazon MSK.
  3. Stream data processing โ€” In this step, you can create streaming ETL jobs that run continuously and consume data from streaming sources such as Amazon Kinesis Data Streams and Amazon MSK. The jobs cleanse and transform the data.
  4. Stream data loadingโ€” The processed data is typically loaded into S3 data lakes or joint database connectivity (JDBC) data stores such as Amazon Redshift or NoSQL data sources such as Amazon DynamoDB or Amazon OpenSearch Service. After the data is loaded, the data can be consumed using services such as Amazon QuickSight, Amazon Athena, Amazon SageMaker, Amazon Managed Grafana, and so on.
  5. Amazon QuickSight โ€” Amazon QuickSight allows everyone in your organization to understand your data by asking questions in their native language, exploring through interactive dashboards, or automatically looking for patterns and outliers powered by ML.
  6. Amazon Athenaโ€” Amazon Athena provides capability for ad hoc querying capability on the data stored in the data lake.
  7. Amazon SageMaker โ€” Amazon SageMaker and AWS AI services can be used to build, train, and deploy ML models, and add intelligence to your applications.
  8. Amazon Managed Grafana โ€” Amazon Managed Grafana is an open-source analytics platform that can be used to query, visualize, alert on, and understand metrics, no matter where they are stored.
  9. Logging, monitoring, and notification โ€” Amazon CloudWatch can be used for monitoring, Amazon SNS can be used for notification, and AWS CloudTrail can be used for event logging.

Was this page helpful?