DBMS > ClickHouse vs. Dgraph vs. Microsoft Azure Data Explorer vs. Oracle Berkeley DB

System Properties Comparison ClickHouse vs. Dgraph vs. Microsoft Azure Data Explorer vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

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.

Distributed and scalable native Graph DBMS

Fully managed big data interactive analytics platform

Widely used in-process key-value store

Primary database model

column oriented

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Time Series DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

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

Website

clickhouse.com

dgraph.io

azure.microsoft.com/services/data-explorer

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

Technical documentation

clickhouse.com/docs

dgraph.io/docs

docs.microsoft.com/en-us/azure/data-explorer

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

Developer

Clickhouse Inc.

Dgraph Labs, Inc.

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2019

1994

Current release

v24.3.2.23-lts, April 2024

cloud service with continuous releases

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

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.

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

C++

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

Server operating systems

FreeBSD
Linux
macOS

Linux
OS X
Windows

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

schema-free

Fixed schema with schema-less datatypes (dynamic)

schema-free

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

Kusto Query Language (KQL), SQL subset

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP 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

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

.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

Yes, possible languages: KQL, Python, R

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

key based and custom

yes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Synchronous replication via Raft

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

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

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.

Planned for future releases

Azure Active Directory Authentication

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.