DBMS > Apache Druid vs. Geode vs. Google BigQuery vs. Quasardb

System Properties Comparison Apache Druid vs. Geode vs. Google BigQuery vs. Quasardb

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

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

Large scale data warehouse service with append-only tables

Distributed, high-performance timeseries database

Primary database model

Relational DBMS
Time Series DBMS

Key-value store

Relational DBMS

Time Series DBMS

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	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	61.90
Rank	#19	Overall
	#13	Relational DBMS

Score	0.19
Rank	#327	Overall
	#30	Time Series DBMS

Website

druid.apache.org

geode.apache.org

cloud.google.com/bigquery

quasar.ai

Technical documentation

druid.apache.org/docs/latest/design

geode.apache.org/docs

cloud.google.com/bigquery/docs

doc.quasar.ai/master

Developer

Apache Software Foundation and contributors

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

Google

quasardb

Initial release

2012

2002

2010

2009

Current release

29.0.1, April 2024

1.1, February 2017

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C++

Server operating systems

Linux
OS X
Unix

All OS with a Java VM

the JDK (8 or later) is also required

hosted

BSD
Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

with tags

SQL

Support of SQL

SQL for querying

SQL-like query language (OQL)

yes

SQL-like query language

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java Client API
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Sharding

consistent hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

Source-replica replication with selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using LevelDB

In-memory capabilities

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

yes

Transient mode

User concepts

Access control

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

Access rights per client and object definable

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

Google Cloud Identity & Access Management (IAM)

Cryptographically strong user authentication and audit trail

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.