StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Utilities
  3. Background Jobs
  4. Message Queue
  5. AWS Glue vs StreamSets

AWS Glue vs StreamSets

OverviewDecisionsComparisonAlternatives

Overview

StreamSets
StreamSets
Stacks53
Followers133
Votes0
AWS Glue
AWS Glue
Stacks461
Followers819
Votes9

AWS Glue vs StreamSets: What are the differences?

Introduction: AWS Glue and StreamSets are two popular data integration tools used for ETL (Extract, Transform, and Load) processes in data pipelines. While both serve similar purposes, there are key differences between them that make each suitable for different use cases.

  1. Scalability: AWS Glue is a serverless ETL service provided by Amazon Web Services. It automatically scales resources based on the input workload, which makes it well-suited for handling large datasets and high-throughput scenarios. On the other hand, StreamSets is a data integration platform that can be deployed on-premises or in the cloud. Its scalability is more manual, as users have to manually provision resources as per their requirements.

  2. Ease of Use: AWS Glue offers a visual interface and a code generation feature that automatically generates ETL code for users. This allows users to create and manage ETL jobs quickly and easily, with minimal coding skills required. StreamSets, on the other hand, offers a visual drag-and-drop interface that enables users to create data pipelines easily, but it also provides a more advanced mode for users who prefer writing code.

  3. Data Source Compatibility: AWS Glue supports a wide range of data sources, including popular databases, data lakes, and streaming services, making it highly compatible with various data environments. StreamSets also supports a wide range of data sources and targets, but it is particularly known for its compatibility with big data platforms like Apache Kafka and Hadoop.

  4. Real-Time Processing: StreamSets is specifically designed for real-time data integration and streaming analytics. It provides advanced features like event-driven data pipelines and support for Apache Kafka, making it well-suited for real-time data ingestion and processing scenarios. AWS Glue, on the other hand, is more focused on batch processing and scheduled ETL jobs, although it can also handle streaming data with the help of AWS Glue Streaming ETL jobs.

  5. Data Transformation Capabilities: AWS Glue provides a set of built-in transformations and data cleaning functions that can be easily applied to transform and enrich data during the ETL process. It also supports custom transformations using Python or Scala, giving users more flexibility in data transformation tasks. StreamSets also offers a wide range of built-in processors and transformers, as well as the ability to write custom code, but it is more focused on data movement and integration rather than extensive data transformations.

  6. Pricing Model: AWS Glue follows a pay-as-you-go pricing model, where users are charged based on the number of job executions and the amount of data processed. StreamSets, on the other hand, follows a subscription-based pricing model, where users pay for licenses and support based on their usage and deployment needs.

In summary, AWS Glue and StreamSets have key differences in terms of scalability, ease of use, data source compatibility, real-time processing capabilities, data transformation capabilities, and pricing models.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on StreamSets, AWS Glue

Vamshi
Vamshi

Data Engineer at Tata Consultancy Services

May 29, 2020

Needs adviceonPySparkPySparkAzure Data FactoryAzure Data FactoryDatabricksDatabricks

I have to collect different data from multiple sources and store them in a single cloud location. Then perform cleaning and transforming using PySpark, and push the end results to other applications like reporting tools, etc. What would be the best solution? I can only think of Azure Data Factory + Databricks. Are there any alternatives to #AWS services + Databricks?

269k views269k
Comments
datocrats-org
datocrats-org

Jul 29, 2020

Needs adviceonAmazon EC2Amazon EC2TableauTableauPowerBIPowerBI

We need to perform ETL from several databases into a data warehouse or data lake. We want to

  • keep raw and transformed data available to users to draft their own queries efficiently
  • give users the ability to give custom permissions and SSO
  • move between open-source on-premises development and cloud-based production environments

We want to use inexpensive Amazon EC2 instances only on medium-sized data set 16GB to 32GB feeding into Tableau Server or PowerBI for reporting and data analysis purposes.

319k views319k
Comments
Pavithra
Pavithra

Mar 12, 2020

Needs adviceonAmazon S3Amazon S3Amazon AthenaAmazon AthenaAmazon RedshiftAmazon Redshift

Hi all,

Currently, we need to ingest the data from Amazon S3 to DB either Amazon Athena or Amazon Redshift. But the problem with the data is, it is in .PSV (pipe separated values) format and the size is also above 200 GB. The query performance of the timeout in Athena/Redshift is not up to the mark, too slow while compared to Google BigQuery. How would I optimize the performance and query result time? Can anyone please help me out?

522k views522k
Comments

Detailed Comparison

StreamSets
StreamSets
AWS Glue
AWS Glue

An end-to-end data integration platform to build, run, monitor and manage smart data pipelines that deliver continuous data for DataOps.

A fully managed extract, transform, and load (ETL) service that makes it easy for customers to prepare and load their data for analytics.

Only StreamSets provides a single design experience for all design patterns (batch, streaming, CDC, ETL, ELT, and ML pipelines) for 10x greater developer productivity; smart data pipelines that are resilient to change for 80% less breakages; and a single pane of glass for managing and monitoring all pipelines across hybrid and cloud architectures to eliminate blind spots and control gaps.
Easy - AWS Glue automates much of the effort in building, maintaining, and running ETL jobs. AWS Glue crawls your data sources, identifies data formats, and suggests schemas and transformations. AWS Glue automatically generates the code to execute your data transformations and loading processes.; Integrated - AWS Glue is integrated across a wide range of AWS services.; Serverless - AWS Glue is serverless. There is no infrastructure to provision or manage. AWS Glue handles provisioning, configuration, and scaling of the resources required to run your ETL jobs on a fully managed, scale-out Apache Spark environment. You pay only for the resources used while your jobs are running.; Developer Friendly - AWS Glue generates ETL code that is customizable, reusable, and portable, using familiar technology - Scala, Python, and Apache Spark. You can also import custom readers, writers and transformations into your Glue ETL code. Since the code AWS Glue generates is based on open frameworks, there is no lock-in. You can use it anywhere.
Statistics
Stacks
53
Stacks
461
Followers
133
Followers
819
Votes
0
Votes
9
Pros & Cons
Cons
  • 2
    No user community
  • 1
    Crashes
Pros
  • 9
    Managed Hive Metastore
Integrations
HBase
HBase
Databricks
Databricks
Amazon Redshift
Amazon Redshift
MySQL
MySQL
gRPC
gRPC
Google BigQuery
Google BigQuery
Amazon Kinesis
Amazon Kinesis
Cassandra
Cassandra
Hadoop
Hadoop
Redis
Redis
Amazon Redshift
Amazon Redshift
Amazon S3
Amazon S3
Amazon RDS
Amazon RDS
Amazon Athena
Amazon Athena
MySQL
MySQL
Microsoft SQL Server
Microsoft SQL Server
Amazon EMR
Amazon EMR
Amazon Aurora
Amazon Aurora
Oracle
Oracle
Amazon RDS for PostgreSQL
Amazon RDS for PostgreSQL

What are some alternatives to StreamSets, AWS Glue?

Kafka

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

RabbitMQ

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Celery

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

Apache Spark

Apache Spark

Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.

ActiveMQ

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Presto

Presto

Distributed SQL Query Engine for Big Data

Apache NiFi

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase