Amazon Redshift vs Citus

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Amazon Redshift
Amazon Redshift

637
319
+ 1
86
Citus
Citus

28
26
+ 1
8
Add tool

Amazon Redshift vs Citus: What are the differences?

What is 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.

What is Citus? Worry-free Postgres for SaaS. Built to scale out. Citus is worry-free Postgres for SaaS. Made to scale out, Citus is an extension to Postgres that distributes queries across any number of servers. Citus is available as open source, as on-prem software, and as a fully-managed service.

Amazon Redshift belongs to "Big Data as a Service" category of the tech stack, while Citus can be primarily classified under "Databases".

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, Citus provides the following key features:

  • Multi-Node Scalable PostgreSQL
  • Built-in Replication and High Availability
  • Real-time Reads/Writes On Multiple Nodes

"Data Warehousing" is the primary reason why developers consider Amazon Redshift over the competitors, whereas "Multi-core Parallel Processing" was stated as the key factor in picking Citus.

Citus is an open source tool with 3.5K GitHub stars and 263 GitHub forks. Here's a link to Citus's open source repository on GitHub.

- No public GitHub repository available -

What is Amazon Redshift?

It is optimized for data sets 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.

What is Citus?

It's an extension to Postgres that distributes data and queries in a cluster of multiple machines. Its query engine parallelizes incoming SQL queries across these servers to enable human real-time (less than a second) responses on large datasets.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose Amazon Redshift?
Why do developers choose Citus?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
      Be the first to leave a con
      What companies use Amazon Redshift?
      What companies use Citus?

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Amazon Redshift?
      What tools integrate with Citus?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      What are some alternatives to Amazon Redshift and Citus?
      Google BigQuery
      Run super-fast, SQL-like queries against terabytes of data in seconds, using the processing power of Google's infrastructure. Load data with ease. Bulk load your data using Google Cloud Storage or stream it in. Easy access. Access BigQuery by using a browser tool, a command-line tool, or by making calls to the BigQuery REST API with client libraries such as Java, PHP or Python.
      Amazon Athena
      Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run.
      Amazon DynamoDB
      With it , you can offload the administrative burden of operating and scaling a highly available distributed database cluster, while paying a low price for only what you use.
      Amazon Redshift Spectrum
      With Redshift Spectrum, you can extend the analytic power of Amazon Redshift beyond data stored on local disks in your data warehouse to query vast amounts of unstructured data in your Amazon S3 “data lake” -- without having to load or transform any data.
      Hadoop
      The Apache Hadoop software library is a framework that allows for the distributed processing of large data sets across clusters of computers using simple programming models. It is designed to scale up from single servers to thousands of machines, each offering local computation and storage.
      See all alternatives
      Decisions about Amazon Redshift and Citus
      Dan Robinson
      Dan Robinson
      at Heap, Inc. · | 16 upvotes · 53.5K views
      atHeapHeap
      Citus
      Citus
      PostgreSQL
      PostgreSQL
      #Databases
      #DataStores

      PostgreSQL was an easy early decision for the founding team. The relational data model fit the types of analyses they would be doing: filtering, grouping, joining, etc., and it was the database they knew best.

      Shortly after adopting PG, they discovered Citus, which is a tool that makes it easy to distribute queries. Although it was a young project and a fork of Postgres at that point, Dan says the team was very available, highly expert, and it wouldn’t be very difficult to move back to PG if they needed to.

      The stuff they forked was in query execution. You could treat the worker nodes like regular PG instances. Citus also gave them a ton of flexibility to make queries fast, and again, they felt the data model was the best fit for their application.

      #DataStores #Databases

      See more
      Dan Robinson
      Dan Robinson
      at Heap, Inc. · | 14 upvotes · 45.7K views
      atHeapHeap
      Heap
      Heap
      Node.js
      Node.js
      Kafka
      Kafka
      PostgreSQL
      PostgreSQL
      Citus
      Citus
      #FrameworksFullStack
      #Databases
      #MessageQueue

      At Heap, we searched for an existing tool that would allow us to express the full range of analyses we needed, index the event definitions that made up the analyses, and was a mature, natively distributed system.

      After coming up empty on this search, we decided to compromise on the “maturity” requirement and build our own distributed system around Citus and sharded PostgreSQL. It was at this point that we also introduced Kafka as a queueing layer between the Node.js application servers and Postgres.

      If we could go back in time, we probably would have started using Kafka on day one. One of the biggest benefits in adopting Kafka has been the peace of mind that it brings. In an analytics infrastructure, it’s often possible to make data ingestion idempotent.

      In Heap’s case, that means that, if anything downstream from Kafka goes down, we won’t lose any data – it’s just going to take a bit longer to get to its destination. We also learned that you want the path between data hitting your servers and your initial persistence layer (in this case, Kafka) to be as short and simple as possible, since that is the surface area where a failure means you can lose customer data. We learned that it’s a very good fit for an analytics tool, since you can handle a huge number of incoming writes with relatively low latency. Kafka also gives you the ability to “replay” the data flow: it’s like a commit log for your whole infrastructure.

      #MessageQueue #Databases #FrameworksFullStack

      See more
      Ankit Sobti
      Ankit Sobti
      CTO at Postman Inc · | 10 upvotes · 73.3K views
      atPostmanPostman
      dbt
      dbt
      Amazon Redshift
      Amazon Redshift
      Stitch
      Stitch
      Looker
      Looker

      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.

      See more
      Interest over time
      Reviews of Amazon Redshift and Citus
      No reviews found
      How developers use Amazon Redshift and Citus
      Avatar of Olo
      Olo uses Amazon RedshiftAmazon Redshift

      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.

      Avatar of Christian Moeller
      Christian Moeller uses Amazon RedshiftAmazon Redshift

      Connected to BI (Pentaho)

      Avatar of Kovid Rathee
      Kovid Rathee uses Amazon RedshiftAmazon Redshift

      OLAP and BI

      How much does Amazon Redshift cost?
      How much does Citus cost?