StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Databases
  4. Databases
  5. Clickhouse vs Scylla

Clickhouse vs Scylla

OverviewDecisionsComparisonAlternatives

Overview

Clickhouse
Clickhouse
Stacks431
Followers543
Votes85
ScyllaDB
ScyllaDB
Stacks143
Followers197
Votes8

Clickhouse vs Scylla: What are the differences?

Introduction

ClickHouse and Scylla are both popular database management systems that are widely used in different applications. While they have some similarities, they also have key differences that set them apart from each other. In this markdown code, we will explore and highlight the main differences between ClickHouse and Scylla.

  1. Data Model and Query Language: ClickHouse is a columnar database that is designed to handle analytical workloads efficiently. It uses a SQL-like query language that supports complex analytical queries and allows users to perform various transformations and aggregations on large datasets. On the other hand, Scylla is a distributed database that is based on Apache Cassandra. It uses CQL (Cassandra Query Language) for querying data and follows the key-value model. This means that Scylla is optimized for high-throughput transactional workloads rather than complex analytics.

  2. Replication and Consistency: ClickHouse supports both synchronous and asynchronous replication methods, allowing users to choose the level of consistency they require for their data. It provides ways to replicate data across different servers and data centers to ensure high availability and fault tolerance. In contrast, Scylla has a built-in distributed architecture that automatically replicates data across multiple nodes. It provides high availability and fault tolerance by replicating data within the same data center or across different data centers, depending on the configuration.

  3. Data Storage and Compression: ClickHouse uses a columnar storage format, which means that data is stored in a column-wise manner rather than row-wise. This allows for efficient compression techniques like dictionary and run-length encoding, resulting in reduced storage space and improved query performance for analytical workloads. Scylla, on the other hand, uses a row-based storage format that is optimized for write-heavy workloads. It incorporates compression techniques like LZ4 and Snappy to reduce the storage footprint of data.

  4. Data Consistency and Durability: ClickHouse provides eventual consistency for data replication, which means that changes made to the data are eventually propagated to all replicas in the cluster. It also provides durability by storing data on disk and supports configurable storage policies for data retention. Scylla, being based on Apache Cassandra, provides tunable consistency levels for data replication. It ensures durability by writing data to disk and also provides the option of replicating data to multiple data centers for increased fault tolerance.

  5. Scalability and Performance: ClickHouse is known for its exceptional performance when it comes to complex analytical queries on large datasets. It can handle high concurrency and provides efficient data compression and caching mechanisms. Scylla, on the other hand, is designed for high-throughput transactional workloads and can handle a massive number of read and write operations in real-time. It provides low-latency responses and supports horizontal scalability by adding more nodes to the cluster.

  6. Community and Ecosystem: ClickHouse has a growing community and a rich ecosystem of tools and integrations that have been developed around it. It is widely adopted by companies for data analytics and reporting purposes. Scylla, being based on Cassandra, also has a large community and ecosystem. It benefits from the existing tools and integrations available for Cassandra and provides seamless integration with other Cassandra-compatible systems.

In summary, ClickHouse is a columnar database optimized for analytical workloads with a SQL-like query language, while Scylla is a distributed database based on Cassandra that is designed for high-throughput transactional workloads. ClickHouse excels in complex analytics and has a growing community, while Scylla provides high availability, low-latency, and scalability for real-time transactional workloads.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Clickhouse, ScyllaDB

Tom
Tom

CEO at Gentlent

Jun 9, 2020

Decided

The Gentlent Tech Team made lots of updates within the past year. The biggest one being our database:

We decided to migrate our #PostgreSQL -based database systems to a custom implementation of #Cassandra . This allows us to integrate our product data perfectly in a system that just makes sense. High availability and scalability are supported out of the box.

387k views387k
Comments
Vinay
Vinay

Head of Engineering

Sep 19, 2019

Needs advice

The problem I have is - we need to process & change(update/insert) 55M Data every 2 min and this updated data to be available for Rest API for Filtering / Selection. Response time for Rest API should be less than 1 sec.

The most important factors for me are processing and storing time of 2 min. There need to be 2 views of Data One is for Selection & 2. Changed data.

174k views174k
Comments

Detailed Comparison

Clickhouse
Clickhouse
ScyllaDB
ScyllaDB

It allows analysis of data that is updated in real time. It offers instant results in most cases: the data is processed faster than it takes to create a query.

ScyllaDB is the database for data-intensive apps that require high performance and low latency. It enables teams to harness the ever-increasing computing power of modern infrastructures – eliminating barriers to scale as data grows.

-
High availability; horizontal scalability; vertical scalability; Cassandra compatible; DynamoDB compatible; wide column; NoSQL; lightweight transactions; change data capture; workload prioritization; shard-per-core; IO scheduler; self-tuning
Statistics
Stacks
431
Stacks
143
Followers
543
Followers
197
Votes
85
Votes
8
Pros & Cons
Pros
  • 21
    Fast, very very fast
  • 11
    Good compression ratio
  • 7
    Horizontally scalable
  • 6
    Utilizes all CPU resources
  • 5
    RESTful
Cons
  • 5
    Slow insert operations
Pros
  • 2
    Replication
  • 1
    Scale up
  • 1
    Distributed
  • 1
    Fewer nodes
  • 1
    Written in C++
Integrations
No integrations available
KairosDB
KairosDB
Wireshark
Wireshark
JanusGraph
JanusGraph
Grafana
Grafana
Hackolade
Hackolade
Prometheus
Prometheus
Kubernetes
Kubernetes
Datadog
Datadog
Kafka
Kafka
Apache Spark
Apache Spark

What are some alternatives to Clickhouse, ScyllaDB?

MongoDB

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

MySQL

MySQL

The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.

PostgreSQL

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

RethinkDB

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase