Need advice about which tool to choose?Ask the StackShare community!
Amazon Redshift vs Dremio: What are the differences?
Introduction
Amazon Redshift and Dremio are both popular data warehouse solutions used by organizations to analyze and process large volumes of data. While they share some similarities, there are key differences between the two platforms that make them unique in their own ways.
Data Processing Model: Amazon Redshift follows a traditional query execution model, where data is stored in a columnar format and processed using massively parallel processing (MPP) techniques. On the other hand, Dremio leverages a distributed SQL-based processing engine that enables interactive querying and analysis directly on various data sources, including cloud storage, NoSQL databases, and relational databases.
Data Virtualization: Dremio offers data virtualization capabilities, allowing users to query and analyze data from multiple sources without the need to move or replicate the data. This enables users to have a unified view of data across different platforms. In contrast, Amazon Redshift requires data to be loaded into its own cluster, which may involve data replication and ETL processes if data is stored in different formats or locations.
Performance Optimization: Amazon Redshift provides various performance optimization techniques such as column compression, parallel query execution, and distribution styles to optimize query performance. Dremio, on the other hand, leverages technologies like Apache Arrow and Apache Parquet to achieve efficient in-memory data processing, which can significantly enhance query performance for a wide range of data formats.
Ease of Use: Dremio emphasizes ease of use with its intuitive user interface and SQL-based query interface. It provides a self-service data exploration and data cataloging experience for business users, enabling them to easily discover, access, and analyze data. Amazon Redshift, while still user-friendly, requires SQL knowledge and may involve more configuration and management tasks like cluster scaling and data loading.
Cost Model: Amazon Redshift follows a pay-as-you-go pricing model, where users pay for the compute resources and storage they consume. The cost can scale with the size of the data and the complexity of queries. Dremio also offers a usage-based pricing model but focuses on minimizing cloud costs through its efficient query engine, smart caching, and data lake acceleration capabilities.
Integrations and Ecosystem: Amazon Redshift has a well-established ecosystem and integrates seamlessly with other AWS services like S3, Glue, and Athena, providing a comprehensive data analytics platform in the AWS ecosystem. Dremio, on the other hand, offers broader integration options with various data sources and tools, allowing users to connect to their preferred repositories and use their preferred data visualization or business intelligence tools for analysis.
In Summary, Amazon Redshift and Dremio differ in their data processing model, data virtualization capabilities, performance optimization techniques, ease of use, cost model, and integrations. These differences make each platform suitable for different use cases and provide organizations with options based on their specific needs.
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.
I am trying to build a data lake by pulling data from multiple data sources ( custom-built tools, excel files, CSV files, etc) and use the data lake to generate dashboards.
My question is which is the best tool to do the following:
- Create pipelines to ingest the data from multiple sources into the data lake
- Help me in aggregating and filtering data available in the data lake.
- Create new reports by combining different data elements from the data lake.
I need to use only open-source tools for this activity.
I appreciate your valuable inputs and suggestions. Thanks in Advance.
Hi Karunakaran. I obviously have an interest here, as I work for the company, but the problem you are describing is one that Zetaris can solve. Talend is a good ETL product, and Dremio is a good data virtualization product, but the problem you are describing best fits a tool that can combine the five styles of data integration (bulk/batch data movement, data replication/data synchronization, message-oriented movement of data, data virtualization, and stream data integration). I may be wrong, but Zetaris is, to the best of my knowledge, the only product in the world that can do this. Zetaris is not a dashboarding tool - you would need to combine us with Tableau or Qlik or PowerBI (or whatever) - but Zetaris can consolidate data from any source and any location (structured, unstructured, on-prem or in the cloud) in real time to allow clients a consolidated view of whatever they want whenever they want it. Please take a look at www.zetaris.com for more information. I don't want to do a "hard sell", here, so I'll say no more! Warmest regards, Rod Beecham.
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 Dremio
- Nice GUI to enable more people to work with Data3
- Connect NoSQL databases with RDBMS2
- Easier to Deploy2
- Free1
Sign up to add or upvote prosMake informed product decisions
Cons of Amazon Redshift
Cons of Dremio
- Works only on Iceberg structured data1