DBMS > ClickHouse vs. CockroachDB vs. NuoDB

System Properties Comparison ClickHouse vs. CockroachDB vs. NuoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Primary database model

Relational DBMS

Secondary database models

Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	16.25
Rank	#37	Overall
	#22	Relational DBMS

Score	4.85
Rank	#64	Overall
	#36	Relational DBMS

Score	0.85
Rank	#206	Overall
	#98	Relational DBMS

Website

clickhouse.com

www.cockroachlabs.com

www.3ds.com/nuodb-distributed-sql-database

Technical documentation

clickhouse.com/docs

www.cockroachlabs.com/docs

doc.nuodb.com

Developer

Clickhouse Inc.

Cockroach Labs

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2016

2015

2013

Current release

v24.6.2.17-stable, July 2024

24.1.0, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

C++

Server operating systems

FreeBSD
Linux
macOS

Linux
macOS
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

JDBC

ADO.NET
JDBC
ODBC

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Java, SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

data is dynamically stored/cached on the nodes where it is read/written

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication using RAFT

yes

Managed transparently by NuoDB

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

tunable commit protocol

Concurrency

Support for concurrent manipulation of data

yes

MVCC

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Temporary table

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

Role-based access control

Standard SQL roles/ privileges, Administrative Users

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.