Amazon Redshift vs InfluxDB: What are the differences?
Amazon Redshift: Fast, fully managed, petabyte-scale data warehouse service. Redshift makes it simple and cost-effective to efficiently analyze all your data using your existing business intelligence tools. It is optimized for datasets ranging from a few hundred gigabytes to a petabyte or more and costs less than $1,000 per terabyte per year, a tenth the cost of most traditional data warehousing solutions; InfluxDB: An open-source distributed time series database with no external dependencies. InfluxDB is a scalable datastore for metrics, events, and real-time analytics. It has a built-in HTTP API so you don't have to write any server side code to get up and running InfluxDB is designed to be scalable, simple to install and manage, and fast to get data in and out..
Amazon Redshift and InfluxDB are primarily classified as "Big Data as a Service" and "Databases" tools respectively.
Some of the features offered by Amazon Redshift are:
- Optimized for Data Warehousing- It uses columnar storage, data compression, and zone maps to reduce the amount of IO needed to perform queries. Redshift has a massively parallel processing (MPP) architecture, parallelizing and distributing SQL operations to take advantage of all available resources.
- Scalable- With a few clicks of the AWS Management Console or a simple API call, you can easily scale the number of nodes in your data warehouse up or down as your performance or capacity needs change.
- No Up-Front Costs- You pay only for the resources you provision. You can choose On-Demand pricing with no up-front costs or long-term commitments, or obtain significantly discounted rates with Reserved Instance pricing.
On the other hand, InfluxDB provides the following key features:
- Time-Centric Functions
- Scalable Metrics
"Data Warehousing" is the primary reason why developers consider Amazon Redshift over the competitors, whereas "Time-series data analysis" was stated as the key factor in picking InfluxDB.
InfluxDB is an open source tool with 16.6K GitHub stars and 2.37K GitHub forks. Here's a link to InfluxDB's open source repository on GitHub.
According to the StackShare community, Amazon Redshift has a broader approval, being mentioned in 267 company stacks & 63 developers stacks; compared to InfluxDB, which is listed in 116 company stacks and 38 developer stacks.
What is Amazon Redshift?
What is InfluxDB?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon Redshift?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Looker , Stitch , Amazon Redshift , dbt
We recently moved our Data Analytics and Business Intelligence tooling to Looker . It's already helping us create a solid process for reusable SQL-based data modeling, with consistent definitions across the entire organizations. Looker allows us to collaboratively build these version-controlled models and push the limits of what we've traditionally been able to accomplish with analytics with a lean team.
For Data Engineering, we're in the process of moving from maintaining our own ETL pipelines on AWS to a managed ELT system on Stitch. We're also evaluating the command line tool, dbt to manage data transformations. Our hope is that Stitch + dbt will streamline the ELT bit, allowing us to focus our energies on analyzing data, rather than managing it.
We use InfluxDB as a store for our data that gets fed into Grafana. It's ideal for this as it's a lightweight storage engine that can be modified on the fly by scripts without having to log into the server itself and manage tables. The HTTP API also makes it ideal for integrating with frontend services.
Aggressive archiving of historical data to keep the production database as small as possible. Using our in-house soon-to-be-open-sourced ETL library, SharpShifter.
To track time-series of course, utilizing few retention rules and continuous queries to keep time-series data fast and maintanable
InfluxDB ingests information from various sources (mostly Telegraf instances) into one place for monitoring purposes.