DBMS > ClickHouse vs. GridDB vs. jBASE vs. MarkLogic vs. Riak KV

System Properties Comparison ClickHouse vs. GridDB vs. jBASE vs. MarkLogic vs. Riak KV

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.

Scalable in-memory time series database optimized for IoT and Big Data

A robust multi-value DBMS comprising development tools and middleware

Operational and transactional Enterprise NoSQL database

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Time Series DBMS

Multivalue DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Time Series DBMS

Key-value store
Relational DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

clickhouse.com

griddb.net

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.progress.com/marklogic

Technical documentation

clickhouse.com/docs

docs.griddb.net

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

www.progress.com/marklogic/documentation

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Clickhouse Inc.

Toshiba Corporation

Rocket Software (formerly Zumasys)

MarkLogic Corp.

OpenSource, formerly Basho Technologies

Initial release

2016

2013

1991

2001

2009

Current release

v24.4.1.2088-stable, May 2024

5.1, August 2022

5.7

11.0, December 2022

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

restricted free version is available

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

Server operating systems

FreeBSD
Linux
macOS

Linux

AIX
Linux
Windows

Linux
OS X
Windows

Linux
OS X

Data scheme

yes

schema-free

Schema can be enforced

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

optional

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

Secondary indexes

yes

restricted

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL92, SQL-like TQL (Toshiba Query Language)

Embedded SQL for jBASE in BASIC

yes

SQL92

APIs and other access methods

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

HTTP API
Native Erlang Interface

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)
Perl
PHP
Python
Ruby

.Net
Basic
Jabbascript
Java

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

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

Source-replica replication

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

ACID at container level

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

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 for users can be defined per database

Access rights can be defined down to the item level

Role-based access control at the document and subdocument levels

yes, using Riak Security

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» 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.