DBMS > BoltDB vs. ClickHouse vs. Oracle Berkeley DB vs. Oracle NoSQL vs. Tarantool

System Properties Comparison BoltDB vs. ClickHouse vs. Oracle Berkeley DB vs. Oracle NoSQL vs. Tarantool

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Key-value store

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store
Key-value store
Relational DBMS

Secondary database models

Time Series DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

github.com/boltdb/bolt

clickhouse.com

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

www.oracle.com/database/nosql/technologies/nosql

www.tarantool.io

Technical documentation

clickhouse.com/docs

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.tarantool.io/en/doc

Developer

Clickhouse Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle

Initial release

2013

2016

1994

2011

2008

Current release

v24.4.1.2088-stable, May 2024

18.1.40, May 2020

24.1, May 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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)

Java

C and C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
Solaris SPARC/x86

BSD
Linux
macOS

Data scheme

schema-free

yes

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

optional

string, double, decimal, uuid, integer, blob, boolean, datetime

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 DML and DDL statements

Full-featured ANSI SQL support

APIs and other access methods

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

RESTful HTTP API

Open binary protocol

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

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

Lua, C and SQL stored procedures

Triggers

yes

only for the SQL API

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

none

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

configurable

ACID within a storage node (=shard)

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

off heap cache

yes, full featured in-memory storage engine with persistence

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.

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.