DBMS > ClickHouse vs. Google Cloud Datastore vs. H2 vs. JanusGraph vs. MonetDB

System Properties Comparison ClickHouse vs. Google Cloud Datastore vs. H2 vs. JanusGraph vs. MonetDB

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

A relational database management system that stores data in columns

Primary database model

Secondary database models

Time Series DBMS

Spatial DBMS

Document store
Spatial DBMS

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

Score	15.55
Rank	#38	Overall
	#23	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	1.72
Rank	#141	Overall
	#64	Relational DBMS

Website

clickhouse.com

cloud.google.com/datastore

www.h2database.com

janusgraph.org

www.monetdb.org

Technical documentation

clickhouse.com/docs

cloud.google.com/datastore/docs

www.h2database.com/html/main.html

docs.janusgraph.org

www.monetdb.org/Documentation

Developer

Clickhouse Inc.

Google

Thomas Mueller

Linux Foundation; originally developed as Titan by Aurelius

MonetDB BV

Initial release

2016

2008

2005

2017

2004

Current release

v24.4.1.2088-stable, May 2024

2.2.220, July 2023

0.6.3, February 2023

Dec2023 (11.49), December 2023

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

Apache 2.0

Open Source

Mozilla Public License 2.0

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

C++

Java

Server operating systems

FreeBSD
Linux
macOS

hosted

All OS with a Java VM

Linux
OS X
Unix
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language (GQL)

yes

SQL 2003 with some extensions

APIs and other access methods

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

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

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

Java

Clojure
Java
Python

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

Server-side scripts

Stored procedures

yes

using Google App Engine

Java Stored Procedures and User-Defined Functions

yes

yes, in SQL, C, R

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding via remote tables

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 using Paxos

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

none

Source-replica replication available in experimental status

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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.

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

User authentification and security via Rexster Graph Server

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.