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
11th
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
5.7
Number of Reviews
23
Ranking in other categories
NoSQL Databases (7th), In-Memory Data Store Services (1st)
 

Mindshare comparison

As of July 2025, in the Vector Databases category, the mindshare of ClickHouse is 3.8%, up from 1.4% 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

"The tool's most valuable feature is a database. It supports portal APIs and offers good flexibility."
"The main feature of ClickHouse is the optimizer because we had too many records to deduplicate, and the optimizer took this task by itself."
"The tool is column-based and infinitely scalable."
"ClickHouse is open source with no vendor lock-in, providing excellent freedom to choose any vendor without restrictions."
"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 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."
"If you have a real-time basis, you should take a look at ClickHouse because it works on a vector database, and the querying is super fast compared to traditional databases."
"I use Redis mostly to cache repeated data that is required."
"The ability to fetch and save data quickly is valuable."
"Redis is a simple service that does what it promises."
"The in-memory data makes it fast."
"Redis acts as an in-memory search tool that improves the speed of operations."
"The product offers fast access to my database."
"The online interface is very fast and easy to use."
"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."
 

Cons

"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."
"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."
"We had a lot of troubles while deploying a whole 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."
"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."
"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."
"ClickHouse has its own concept of database triggers and doesn't support traditional database triggers."
"The main issue is the lack of documentation. Many features are available but are not fully documented, which can make finding information challenging."
"In future releases, I would like Redis to provide its users with an option like schema validation. Currently, the solution lacks to offer such functionality."
"The initial setup took some time as our technical team needed to familiarize themselves with Redis."
"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."
"There are some features from MongoDB that I would like to see included in Redis to enhance its overall efficiency, such as the ability to perform remote behaviour. MongoDB is more efficient in handling updates than deletions and is quicker in processing updates, but it can be slower regarding deletions. This can sometimes pose a challenge, especially when dealing with large datasets or frequent data manipulations that involve deletions. In such cases, I often rewrite columns or update values instead of directly deleting data, as it can be more efficient."
"It's actually quite expensive."
"Sometimes, we use Redis as a cluster, and the clusters can sometimes suffer some issues and bring some downtime to your application."
"If we use a lot of data, it will eventually cost us a lot."
"Redis should have an option to operate without Docker on a local PC."
 

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 has an open-source version, which is free to use and has almost all the features."
"The tool is open-source."
"The tool is free."
"We used the free, community version of ClickHouse."
"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."
"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."
"Redis is not an overpriced solution."
"Redis is an open-source product."
"Redis is an open-source solution. There are not any hidden fees."
"The tool is open-source. There are no additional costs."
"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.
864,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
23%
Financial Services Firm
17%
Educational Organization
10%
Manufacturing Company
9%
Financial Services Firm
24%
Computer Software Company
13%
Educational Organization
7%
Comms Service Provider
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?
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....
What is your primary use case for ClickHouse?
I have experience in ClickHouse ( /products/clickhouse-reviews ), and we also use Apache Druid ( /products/druid-reviews ), which has corporate support from Druid ( /products/druid-reviews ), along...
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?
The disadvantage of Redis is that it's a little bit hard to have too many clusters or too many nodes and create the clusters. The sync between the nodes is easier to implement with Couchbase, for e...
What is your primary use case for Redis?
Redis is used for a part of a booking engine for travel, specifically for the front part to get some sessions and information about the sessions. If a customer or user is using the sites in differe...
 

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: July 2025.
864,053 professionals have used our research since 2012.