Need advice about which tool to choose?Ask the StackShare community!
Amazon Redshift vs Druid: What are the differences?
Introduction:
When comparing Amazon Redshift and Druid, it's essential to understand the key differences between the two data storage and processing solutions. Both are popular choices for handling large volumes of data and providing analytical capabilities, but they have distinct features that make them suitable for different use cases.
Architecture: Amazon Redshift is a fully managed data warehouse service that uses a columnar storage architecture optimized for complex queries and high-performance analytics. In contrast, Druid is a distributed, column-oriented, real-time data store designed to handle high data ingestion rates and provide sub-second queries for time-series data.
Query Processing: Amazon Redshift uses traditional SQL queries and can handle complex joins, aggregations, and window functions efficiently. On the other hand, Druid supports SQL-like queries along with Apache Druid Query Language (DQL) for real-time and interactive analytics. It provides faster query response times for time-series data by utilizing a specialized query engine.
Data Ingestion: Amazon Redshift allows data to be loaded from various sources using tools like AWS Glue, Amazon Kinesis, and Amazon S3. Druid is designed for real-time data ingestion and can directly ingest streaming data from sources like Kafka and Apache Storm. It supports continuous data ingestion and enables interactive analytics on fresh data.
Scalability: Amazon Redshift offers on-demand scalability by automatically managing storage expansion, compute resources, and query optimization. Druid is horizontally scalable and can be easily scaled out by adding more nodes to the cluster, providing the ability to handle massive data sets and an increasing number of queries.
Use Cases: Amazon Redshift is well-suited for traditional data warehousing and business intelligence workloads where ad-hoc queries, reporting, and dashboarding are required. Druid is ideal for use cases that demand real-time analytics, event-driven architectures, time-series data analysis, and interactive dashboarding with near real-time insights.
In Summary, Amazon Redshift and Druid cater to different data processing and analytics requirements, with Redshift excelling in traditional data warehousing tasks and Druid providing real-time analytics capabilities for time-series data and event-driven applications.
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.
You could also use AWS Lambda and use Cloudwatch event schedule if you know when the function should be triggered. The benefit is that you could use any language and use the respective database client.
But if you orchestrate ETLs then it makes sense to use Apache Airflow. This requires Python knowledge.
Though we have always built something custom, Apache airflow (https://airflow.apache.org/) stood out as a key contender/alternative when it comes to open sources. On the commercial offering, Amazon Redshift combined with Amazon Kinesis (for complex manipulations) is great for BI, though Redshift as such is expensive.
You may want to look into a Data Virtualization product called Conduit. It connects to disparate data sources in AWS, on prem, Azure, GCP, and exposes them as a single unified Spark SQL view to PowerBI (direct query) or Tableau. Allows auto query and caching policies to enhance query speeds and experience. Has a GPU query engine and optimized Spark for fallback. Can be deployed on your AWS VM or on prem, scales up and out. Sounds like the ideal solution to your needs.
Pros of Amazon Redshift
- Data Warehousing41
- Scalable27
- SQL17
- Backed by Amazon14
- Encryption5
- Cheap and reliable1
- Isolation1
- Best Cloud DW Performance1
- Fast columnar storage1
Pros of Druid
- Real Time Aggregations15
- Batch and Real-Time Ingestion6
- OLAP5
- OLAP + OLTP3
- Combining stream and historical analytics2
- OLTP1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon Redshift
Cons of Druid
- Limited sql support3
- Joins are not supported well2
- Complexity1