DBMS > ClickHouse vs. Oracle Berkeley DB vs. RavenDB vs. SQL.JS vs. Transbase

System Properties Comparison ClickHouse vs. Oracle Berkeley DB vs. RavenDB vs. SQL.JS vs. Transbase

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.

Widely used in-process key-value store

Open Source Operational and Transactional Enterprise NoSQL Document Database

Port of SQLite to JavaScript

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Relational DBMS

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

clickhouse.com

www.oracle.com/database/technologies/related/berkeleydb.html

ravendb.net

sql.js.org

www.transaction.de/en/products/transbase.html

Technical documentation

clickhouse.com/docs

docs.oracle.com/cd/E17076_05/html/index.html

ravendb.net/docs

sql.js.org/documentation/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Clickhouse Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Hibernating Rhinos

Alon Zakai

enhancements implemented by others

Transaction Software GmbH

Initial release

2016

1994

2010

2012

1987

Current release

v24.4.1.2088-stable, May 2024

18.1.40, May 2020

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

AGPL version 3, commercial license available

Open Source

commercial

free development license

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.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

C, Java, C++ (depending on the Berkeley DB edition)

JavaScript

C and C++

Server operating systems

FreeBSD
Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS
Raspberry Pi
Windows

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

SQL interfaced based on SQLite is available

SQL-like query language (RQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

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

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

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

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

JavaScript

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

except by serializing a db to a file

yes

In-memory capabilities

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

yes

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.

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

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.