Cassandra vs ClickHouse comparison

"Cassandra is good. It's better than CouchDB, and we are using it in parallel with CouchDB. Cassandra looks better and is more user-friendly."

"Cassandra has some features that are more useful for specific use cases where you have time series where you have huge amounts of writes. That should be quick, but not specifically the reads. We needed to have quicker reads and writes and this is why we are using Cassandra right now."

"The most valuable features are the counter features and the NoSQL schema. It also has good scalability. You can scale Cassandra to any finite level."

"The most valuable features of this solution are its speed and distributed nature."

"The most valuable features of Cassandra are its scaling capabilities and its non-SQL nature capabilities."

"The solution's database capabilities are very good."

"The use of Cassandra in real-time data analytics has been pivotal for our e-commerce platform. As our platform operates 24/7, providing services to sellers and customers alike, the need for real-time updates is paramount."

"Our primary use case for the solution is testing."

"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."

"The main feature of ClickHouse is the optimizer because we had too many records to deduplicate, and the optimizer took this task by itself."

"It's easier to work with big data and calculations using the product."

"The tool is column-based and infinitely scalable."

"ClickHouse is a user-friendly solution that tries to be compatible with SQL standards."

"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."

"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 secondary index in Cassandra was a bit problematic and could be improved."

"There were challenges with the query language and the development interface. The query language, in particular, could be improved for better optimization. These challenges were encountered while using the Java SDK."

"We experience configuration issues when accommodating the volumes we require, which often necessitates consultation with the Cassandra development team."

"The solution is not easy to use because it is a big database and you have to learn the interface. This is the case though in most of these solutions."

"Interface is not user friendly."

"The initial setup of Cassandra can be difficult in the configuration. There might be a need to have assistance. The implementation process can six months for connecting to certain databases."

"It can be difficult to analyze what's going on inside of the database relative to other databases. It can also be difficult to troubleshoot sometimes."

"The solution doesn't have joins between tables so you need other tools for that."

"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."

"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."

"One issue is that you need persistent volumes. Otherwise, if one system goes down, you lose data in that 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."

"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."

"ClickHouse has its own concept of database triggers and doesn't support traditional database triggers."

"I would like ClickHouse to work more on integration with third-party tools."

"I don't have the specific numbers on pricing, but it was fairly priced."

"Cassandra is a free open source solution, but there is a commercial version available called DataStax Enterprise."

"There are licensing fees that must be paid, but I'm not sure if they are paid monthly or yearly."

"We are using the open-source version of Cassandra, the solution is free."

"We pay for a license."

"I use the tool's open-source version."

"ClickHouse Cloud is not expensive compared to other databases, costing a few dollars per month while providing fast performance."

"The tool is free."

"ClickHouse has an open-source version, which is free to use and has almost all the features."

"The tool is open-source."

"We used the free, community version of ClickHouse."

"If you have an in-house deployment on Kubernetes or something, it's going to be very cheap since you'll be managing everything."

"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."