DBMS > Citus vs. ClickHouse vs. Oracle Berkeley DB vs. Sadas Engine vs. Sphinx

System Properties Comparison Citus vs. ClickHouse vs. Oracle Berkeley DB vs. Sadas Engine vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Search engine

Secondary database models

Document store

Time Series DBMS

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

Score	2.15
Rank	#123	Overall
	#60	Relational DBMS

Score	16.20
Rank	#37	Overall
	#23	Relational DBMS

Score	2.52
Rank	#114	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

www.citusdata.com

clickhouse.com

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

www.sadasengine.com

sphinxsearch.com

Technical documentation

docs.citusdata.com

clickhouse.com/docs

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

sphinxsearch.com/docs

Developer

Clickhouse Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SADAS s.r.l.

Sphinx Technologies Inc.

Initial release

2010

2016

1994

2006

2001

Current release

8.1, December 2018

v24.3.2.23-lts, April 2024

18.1.40, May 2020

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Apache 2.0

Open Source

commercial license available

commercial

free trial version available

Open Source

GPL version 2, commercial licence 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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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.

Implementation language

C++

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

C++

Server operating systems

Linux

FreeBSD
Linux
macOS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
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

specific XML type available, but no XML query functionality

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

standard, with numerous extensions

Close to ANSI SQL (SQL/JSON + extensions)

yes

SQL interfaced based on SQLite is available

yes

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

JDBC
ODBC
Proprietary protocol

Proprietary protocol

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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
C#
C++
Groovy
Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

key based and custom

none

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

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

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

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, groups and roles 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.