Try our new research platform with insights from 80,000+ expert users

ClickHouse vs Redis comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

ClickHouse
Ranking in Vector Databases
10th
Average Rating
8.8
Reviews Sentiment
7.8
Number of Reviews
11
Ranking in other categories
Open Source Databases (6th)
Redis
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
8.0
Number of Reviews
22
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st)
 

Mindshare comparison

As of May 2025, in the Vector Databases category, the mindshare of ClickHouse is 3.6%, up from 1.1% compared to the previous year. The mindshare of Redis is 4.9%, down from 6.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases
 

Featured Reviews

Aswini Atibudhi - PeerSpot reviewer
Provides real-time data insights with high flexibility and responsive support
The basic challenge for ClickHouse is the documentation, which isn't ideal, but it's mature and stable with more columnar storage, compression, and parallel processing, making it the best for OLAP. In terms of improvements, it's not designed for very frequent small writes, making it less scalable in write-intensive workloads, and it's not flourishing in transactional use cases or when ingesting streaming data, such as batching or buffering, which is something ClickHouse will improve.
Yaseer Arafat - PeerSpot reviewer
Unmatched Performance and Scalability for Modern Applications
Redis has room for improvement in a few areas. Enhanced tools for managing and monitoring clusters would be beneficial, as would built-in security mechanisms like advanced encryption and granular access controls. Simplifying setup and configuration could make Redis more accessible to new users. Introducing more enterprise-grade features, such as better multi-tenancy support and improved backup and restore capabilities, would also be advantageous. For the next release, it would be great to see enhanced cluster management tools, native multi-region supports for better data redundancy, integrated analytics for deeper insights, AI and ML integration features, and improved developer experience through enhanced SDKs and tools.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"ClickHouse is much faster than traditional databases like MySQL and MongoDB. Its column-row searching strategy makes it very efficient. With ClickHouse, we can manage multiple databases, automatically insert data from other databases and delete data as needed. It supports real-time query performance, allowing simultaneous data insertion and retrieval. ClickHouse has improved significantly over the past two years, adding more functions and queries, as well as top functionality."
"The tool is column-based and infinitely scalable."
"ClickHouse is very easy to use; one of the good features is that it has joins, which were not present in Druid, and Druid was quite expensive, especially with our applications at Sam's Club utilizing ClickHouse very quickly."
"The best thing about the tool is that I can set it up on my computer and run queries without depending on the cloud. This is why I use it every day."
"We faced a challenge with deploying ClickHouse onto Kubernetes. Recently, we've been using ClickHouse Cloud, and the main issue is the high cost of the cloud service. The pricing isn't very competitive, especially for startups. I would instead buy a server and self-host if I have enough disk space. Besides that, ClickHouse has done very well, with clear goals and effective execution."
"It's easier to work with big data and calculations using the product."
"The main feature of ClickHouse is the optimizer because we had too many records to deduplicate, and the optimizer took this task by itself."
"ClickHouse is a user-friendly solution that tries to be compatible with SQL standards."
"I find Redis valuable primarily for its caching capabilities, particularly in handling cache requests effectively. Its simplicity in managing key-value pairs for caching is one of its strengths, making it a preferred choice over more complex databases like MongoDB for specific use cases. However, I haven't explored Redis extensively for managing complex data structures beyond caching, as MongoDB might be more suitable for such scenarios."
"The ability to fetch and save data quickly is valuable."
"I use Redis mostly to cache repeated data that is required."
"Redis provides an easy setup and operation process, allowing users to quickly connect and use it without hassle."
"Redis is a simple, powerful, and fast solution."
"Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you use Redis efficiently."
"The solution is fast, provides good performance, and is not too expensive."
"The in-memory data makes it fast."
 

Cons

"I would like ClickHouse to work more on integration with third-party tools."
"There aren't too many improvements I'd suggest for ClickHouse as it covers all my needs. There are just a few technical issues. For example, sometimes, when you want to get unique values and use certain tables, they don't work as expected. But it's not a major problem."
"There are some areas where ClickHouse could improve. Specifically, we encountered incompatibilities with its SQL syntax when migrating queries from MySQL or SQL to ClickHouse. This difference in details made it challenging to figure out the exact issues. Additionally, we faced difficulties due to the lack of a proper Django driver for ClickHouse, unlike MySQL, which Django supports out of the box."
"The aggregation capability is a valuable feature. It's highly efficient, allowing us to review entire transaction histories and user activities in the market. We've tried MongoDB, Postgres, MariaDB, and BigQuery, but ClickHouse is the most cost-efficient solution for collecting data at high speeds with minimal cost. We even used ClickHouse Cloud for a month, and it proved to be a great setup, especially for startups looking to handle big data. For example, if there is a need for 2-4 terabytes of data and around 40 billion rows with reasonable computing speed and latency, ClickHouse is ideal. Regarding the real-time query performance of ClickHouse, when using an API server to query it, I achieved query results in less than twenty milliseconds in some of my experiments with one billion rows. However, it depends on the scenario since ClickHouse has limitations in handling mutations. Additionally, one of ClickHouse's strengths is its compression capability. Our experimental server has only four terabytes, and ClickHouse effectively compresses data, allowing us to store large amounts of data at high speed. This compression efficiency is a significant advantage of using ClickHouse."
"Initially, I faced challenges integrating ClickHouse, particularly with inserting data from ActiveMQ, which caused duplicates. However, after adjusting the ClickHouse settings, the issue was resolved and there were no more duplicates."
"We had a lot of troubles while deploying a whole cluster."
"One issue is that you need persistent volumes. Otherwise, if one system goes down, you lose data in that cluster."
"If you join our team, it should be easy for you to use ClickHouse, especially if you are a developer. However, you need to read the documentation and understand the problems you are trying to solve."
"Redis should have an option to operate without Docker on a local PC."
"The solution's pricing for a local installation is very expensive."
"The initial setup of Redis was difficult, with a rating of two or three out of ten."
"There is a lack of documentation on the scalability of the solution."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"Redis could improve its efficiency in handling locally stored data, not just Amazon Cloud or Google Cloud."
"The only thing is the lack of a GUI application. There was a time when we needed to resolve an issue in production. If we had a GUI, it would have been easier."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
 

Pricing and Cost Advice

"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."
"ClickHouse has an open-source version, which is free to use and has almost all the features."
"The tool is free."
"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."
"The tool is open-source."
"For pricing, if you use the self-hosted version, it would be free. Cloud services pricing would be an eight out of ten. I try to minimize costs but still have to monitor usage."
"We used the free, community version of ClickHouse."
"The tool is open-source. There are no additional costs."
"We saw an ROI. It made the processing of our transactions faster."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
26%
Financial Services Firm
16%
Educational Organization
12%
Manufacturing Company
9%
Financial Services Firm
22%
Computer Software Company
14%
Educational Organization
7%
Manufacturing Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What is your experience regarding pricing and costs for ClickHouse?
ClickHouse is open source without direct fees, unlike other databases that have hidden fees or restrict hosting to their platforms. The open-source nature of ClickHouse allows for complete flexibil...
What needs improvement with ClickHouse?
A significant area for improvement is the documentation, which is not comprehensive and lacks centralized resources, making it difficult to find information. Additionally, ClickHouse lacks robust s...
What is your primary use case for ClickHouse?
The main use case for ClickHouse is as a data warehouse for handling large volumes of data that exceed the capabilities of traditional databases like Postgres. I use it for creating dashboards and ...
What do you like most about Redis?
Redis is better tested and is used by large companies. I haven't found a direct alternative to what Redis offers. Plus, there are a lot of support and learning resources available, which help you u...
What needs improvement with Redis?
There are a few areas where Redis could improve. The pub-sub capabilities could be optimized to handle network sessions better, as there are challenges with maintaining sessions between clients and...
What is your primary use case for Redis?
We use Redis ( /products/redis-reviews ) for several purposes, including ranking, counting, saving, sharing, caching, and setting time-to-live notifications. These functionalities are employed acro...
 

Comparisons

 

Also Known As

No data available
Redis Enterprise
 

Overview

 

Sample Customers

Information Not Available
1. Twitter 2. GitHub 3. StackOverflow 4. Pinterest 5. Snapchat 6. Craigslist 7. Digg 8. Weibo 9. Airbnb 10. Uber 11. Slack 12. Trello 13. Shopify 14. Coursera 15. Medium 16. Twitch 17. Foursquare 18. Meetup 19. Kickstarter 20. Docker 21. Heroku 22. Bitbucket 23. Groupon 24. Flipboard 25. SoundCloud 26. BuzzFeed 27. Disqus 28. The New York Times 29. Walmart 30. Nike 31. Sony 32. Philips
Find out what your peers are saying about ClickHouse vs. Redis and other solutions. Updated: April 2025.
851,604 professionals have used our research since 2012.