DBMS > BaseX vs. ClickHouse vs. Geode vs. Oracle Berkeley DB vs. TerarkDB

System Properties Comparison BaseX vs. ClickHouse vs. Geode vs. Oracle Berkeley DB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Widely used in-process key-value store

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Native XML DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Secondary database models

Time Series DBMS

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

Score	1.84
Rank	#135	Overall
	#4	Native XML DBMS

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

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

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

basex.org

clickhouse.com

geode.apache.org

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

github.com/bytedance/terarkdb

Technical documentation

docs.basex.org

clickhouse.com/docs

geode.apache.org/docs

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

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

BaseX GmbH

Clickhouse Inc.

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

ByteDance, originally Terark

Initial release

2007

2016

2002

1994

2016

Current release

11.0, June 2024

v24.4.1.2088-stable, May 2024

1.1, February 2017

18.1.40, May 2020

License

Commercial or Open Source

Open Source

BSD license

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

commercial license available

commercial

restricted open source version available

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
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.
DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.

Implementation language

Java

C++

Java

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

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

XQuery supports types

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)

SQL-like query language (OQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

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

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

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
All JVM based languages
C++
Groovy
Java
Scala

.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++
Java

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

via events

yes

Cache Event Listeners

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

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

Multi-source replication

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

multiple readers, single writer

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

Users with fine-grained authorization concept on 4 levels

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 per client and object definable

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.