DBMS > ClickHouse vs. EJDB vs. Google Cloud Bigtable vs. GridGain

System Properties Comparison ClickHouse vs. EJDB vs. Google Cloud Bigtable vs. GridGain

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Relational DBMS

Document store

Key-value store
Wide column store

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Secondary database models

Time Series DBMS

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	2.97
Rank	#92	Overall
	#15	Key-value stores
	#8	Wide column stores

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Website

clickhouse.com

github.com/Softmotions/ejdb

cloud.google.com/bigtable

www.gridgain.com

Technical documentation

clickhouse.com/docs

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/bigtable/docs

www.gridgain.com/docs/index.html

Developer

Clickhouse Inc.

Softmotions

Google

GridGain Systems, Inc.

Initial release

2016

2012

2015

2007

Current release

v24.6.2.17-stable, July 2024

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

commercial

commercial, open source

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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.

Implementation language

C++

Java, C++, .Net, Python, REST, SQL

Server operating systems

FreeBSD
Linux
macOS

server-less

hosted

Linux
OS X
Solaris
Windows
z/OS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

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

in-process shared library

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

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

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Internal replication in Colossus, and regional replication between two clusters in different zones

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

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

Role-based access control
Security Hooks for custom implementations

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.