DBMS > Apache Druid vs. Google BigQuery vs. Hazelcast vs. IBM Cloudant

System Properties Comparison Apache Druid vs. Google BigQuery vs. Hazelcast vs. IBM Cloudant

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Large scale data warehouse service with append-only tables

A widely adopted in-memory data grid

Database as a Service offering based on Apache CouchDB

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	2.73
Rank	#108	Overall
	#20	Document stores

Website

druid.apache.org

cloud.google.com/bigquery

hazelcast.com

www.ibm.com/products/cloudant

Technical documentation

druid.apache.org/docs/latest/design

cloud.google.com/bigquery/docs

hazelcast.org/imdg/docs

cloud.ibm.com/docs/Cloudant

Developer

Apache Software Foundation and contributors

Google

Hazelcast

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2012

2010

2008

2010

Current release

29.0.1, April 2024

5.3.6, November 2023

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

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.

Implementation language

Java

Erlang

Server operating systems

Linux
OS X
Unix

hosted

All OS with a Java VM

hosted

Data scheme

yes

schema-less columns are supported

yes

schema-free

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

SQL-like query language

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Event Listeners, Executor Services

View functions (Map-Reduce) in JavaScript

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Replicated Map

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

one or two-phase-commit; repeatable reads; read commited

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Role-based access control

Access rights for users can be defined per database

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.