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.7
Number of Reviews
10
Ranking in other categories
Open Source Databases (6th)
Redis
Ranking in Vector Databases
4th
Average Rating
8.8
Reviews Sentiment
8.1
Number of Reviews
21
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st)
 

Mindshare comparison

As of March 2025, in the Vector Databases category, the mindshare of ClickHouse is 2.9%, up from 0.9% compared to the previous year. The mindshare of Redis is 5.0%, down from 7.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Vector Databases
 

Featured Reviews

ArpitShah - PeerSpot reviewer
Open-source freedom with efficient data handling and room for documentation growth
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 support for transactional data, which limits its use as a primary database. My developer experience could be enhanced through better-organized documentation, perhaps by offering a cheat sheet or centralized guide for common setup and usage scenarios.
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

"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."
"The tool's most valuable feature is a database. It supports portal APIs and offers good flexibility."
"The tool is column-based and infinitely scalable."
"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."
"ClickHouse is a user-friendly solution that tries to be compatible with SQL standards."
"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 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."
"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."
"What I like best about Redis is its fast and easy use. It has interesting algorithms like HyperLogLog and provides useful features. It's also good for implementing scalable rate limiting."
"The ability to fetch and save data quickly is valuable."
"Redis is a simple, powerful, and fast solution."
"The most valuable features of Redis are its ease of use and speed. It does not have access to the disc and it is fast."
"The solution's technical support team is good...The solution's initial setup process was straightforward."
"The best thing about Redis is its ability to handle large amounts of data without frequently hitting the database. You can store data in temporary memory, especially for high-volume data."
"The in-memory data makes it fast."
 

Cons

"One issue is that you need persistent volumes. Otherwise, if one system goes down, you lose data in that cluster."
"I would like ClickHouse to work more on integration with third-party tools."
"We had a lot of troubles while deploying a whole cluster."
"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."
"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."
"ClickHouse has its own concept of database triggers and doesn't support traditional database triggers."
"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 main issue is the lack of documentation. Many features are available but are not fully documented, which can make finding information challenging."
"Redis should have an option to operate without Docker on a local PC."
"The development of clusters could improve. Additionally, it would be helpful if it was integrated with Amazon AWS or Google Cloud."
"Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation."
"The solution's pricing for a local installation is very expensive."
"I would prefer it if there was more information available about Redis. That would make it easier for new beginners. Currently, there is a lack of resources."
"If we use a lot of data, it will eventually cost us a lot."
"The tool should improve by increasing its size limits and handling dynamic data better. We use the client ID or associate it with a key for static content. The solution will not be easy for a beginner. Unless you understand SQL data, it will be difficult to understand and use Redis. It also needs to be user-friendly."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
 

Pricing and Cost Advice

"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."
"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."
"The tool is open-source."
"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."
"The tool is free."
"We used the free, community version of ClickHouse."
"ClickHouse has an open-source version, which is free to use and has almost all the features."
"The tool is open-source. There are no additional costs."
"Redis is an open-source solution. There are not any hidden fees."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"We saw an ROI. It made the processing of our transactions faster."
report
Use our free recommendation engine to learn which Vector Databases solutions are best for your needs.
842,592 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
27%
Financial Services Firm
15%
Educational Organization
14%
Manufacturing Company
9%
Financial Services Firm
22%
Computer Software Company
15%
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?
Redis could be improved by introducing a GUI to display key-value pair database information, as it is currently a CLI tool with no visual representation. Additionally, better documentation is neede...
What is your primary use case for Redis?
I use Redis as a tool in building projects, specifically for in-memory caching. My backend API uses Redis to cache information retrieved from the database.
 

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: March 2025.
842,592 professionals have used our research since 2012.