DBMS > ClickHouse vs. Geode vs. IBM Cloudant vs. IBM Db2 warehouse vs. MariaDB

System Properties Comparison ClickHouse vs. Geode vs. IBM Cloudant vs. IBM Db2 warehouse vs. MariaDB

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.

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

Database as a Service offering based on Apache CouchDB

Cloud-based data warehousing service

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Website

clickhouse.com

geode.apache.org

www.ibm.com/products/cloudant

www.ibm.com/products/db2/warehouse

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

Technical documentation

clickhouse.com/docs

geode.apache.org/docs

cloud.ibm.com/docs/Cloudant

mariadb.com/kb/en/library

Developer

Clickhouse Inc.

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

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Initial release

2016

2002

2010

2014

2009

Fork of MySQL, which was first released in 1995

Current release

v24.3.2.23-lts, April 2024

1.1, February 2017

11.3.2, February 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL version 2, commercial enterprise subscription 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++

Java

Erlang

C and C++

Server operating systems

FreeBSD
Linux
macOS

All OS with a Java VM

the JDK (8 or later) is also required

hosted

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

Data scheme

yes

schema-free

yes

Dynamic columns are supported

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.

Import/export of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (OQL)

yes

with proprietary extensions

APIs and other access methods

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

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native 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

.Net
All JVM based languages
C++
Groovy
Java
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

View functions (Map-Reduce) in JavaScript

PL/SQL, SQL PL

yes

PL/SQL compatibility added with version 10.3

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

several options for horizontal partitioning and Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes, on a single node

atomic operations within a document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

In-memory capabilities

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

yes

with MEMORY storage engine

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.