DBMS > Apache Druid vs. ClickHouse vs. Geode vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB

System Properties Comparison Apache Druid vs. ClickHouse vs. Geode vs. Microsoft Azure SQL Database vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used in-process key-value store

Primary database model

Relational DBMS
Time Series DBMS

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

druid.apache.org

clickhouse.com

geode.apache.org

azure.microsoft.com/en-us/products/azure-sql/database

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

Technical documentation

druid.apache.org/docs/latest/design

clickhouse.com/docs

geode.apache.org/docs

docs.microsoft.com/en-us/azure/azure-sql

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

Developer

Apache Software Foundation and contributors

Clickhouse Inc.

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

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2016

2002

2010

1994

Current release

29.0.1, April 2024

v24.4.1.2088-stable, May 2024

1.1, February 2017

V12

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

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

Implementation language

Java

C++

Java

C++

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

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-less columns are supported

yes

schema-free

yes

schema-free

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

SQL for querying

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

JDBC
RESTful HTTP/JSON API

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

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.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

Server-side scripts

Stored procedures

yes

user defined functions

Transact SQL

Triggers

yes

Cache Event Listeners

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

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

Multi-source replication

yes, with always 3 replicas available

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

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.