ClickHouse vs. Scylla

The most important thing when using ClickHouse is to be clear that the scenarios in which you want to use it really are the right ones. Many users think that when a database is very fast for a specific use case, it can be extrapolated to other contexts (most of the time different) in which a previous analysis has not been carried out.

ClickHouse is an analytical database, as such, it should be used for such purposes, where the information is stored correctly, the data volumes are really large and the queries to be performed are not the typical traditional queries on several columns with multiple aggregations. ClickHouse is not the solution for this.

On the other hand, if your case is not one of the above, it is quite possible that ClickHouse can help you. Where ClickHouse shines is when you are looking for aggregation over a particular column in large volumes of data.

Incentivized

Scylla is well suited for high-throughput scenarios where keyed data must be read or written with consistently low latency. It's less appropriate for use cases requiring relational queries, secondary indexes, or more structured data sets.

• Their MergeTree table engine provide impressive performance for data insert in bulk
• Not only data insert but also the way MergeTree engine uses Primary Keys to sort the data and perform data skipping based on the granules its also their secret for ridiculous fast queries
• Data compression its also great
• They provide especial table engines that allow you to read data directly from other sources like S3
• Since its written with C++ you have very granular data types and especial ones like enum, LowCardinality and etc, they save you a lot of storage since are stored as integer values
• ClickHouse functions besides the ones that respect ANSI Standards are also awesome and useful

Incentivized

• Low-latency reads
• CQL has a familiar syntax
• Parity with Cassandra
• Practical features

• Avro data manipulation
• Kafka consistency
• DDL operations errors (by replica configuration)

Incentivized

• Better documentation for best practices (e.g., how to effectively use connection pooling)

Very easy-to-understand syntax--uses CQL (same as Cassandra), which has many similarities to standard SQL. There are some gotchas, however, that must be known during schema development.

The Scylla cloud support team is incredibly responsive and proactive.

ClickHouse outperforms, especially in costs, since its compression/indexing engines are so smart, and even with very low computing power, you can already perform huge analyses of the data.

Incentivized

Scylla has a quick learning curve (same as Cassandra) compared to other proprietary solutions like BigTable. It supports higher throughput and lower latency that other NoSQL databases like MongoDB, which sacrifice those features for more flexibility and unique features.

• Queries that used to take more than 2 minutes now take less than 1 second
• Possibility to analyze use cases in real time (before was impossible)
• The applications are more complete and the users decisions are better

Incentivized

• Addresses latency requirements of our platform