DBMS > Apache Druid vs. CrateDB vs. Google BigQuery

System Properties Comparison Apache Druid vs. CrateDB vs. Google BigQuery

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

Distributed Database based on Lucene

Large scale data warehouse service with append-only tables

Primary database model

Relational DBMS
Time Series DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	0.73
Rank	#224	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#8	Vector DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

druid.apache.org

cratedb.com

cloud.google.com/bigquery

Technical documentation

druid.apache.org/docs/latest/design

cratedb.com/docs

cloud.google.com/bigquery/docs

Developer

Apache Software Foundation and contributors

Crate

Google

Initial release

2012

2013

2010

Current release

29.0.1, April 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

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.

CrateDB Cloud: a distributed SQL database that spreads data and processing across an elastic cluster of shared nothing nodes. CrateDB Cloud enables data insights at scale on Microsoft Azure, AWS and Google Cloud Platform.

Implementation language

Java

Server operating systems

Linux
OS X
Unix

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

hosted

Data scheme

yes

schema-less columns are supported

Flexible Schema (defined schema, partial schema, schema free)

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes, but no triggers and constraints, and PostgreSQL compatibility

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions (Javascript)

user defined functions

in JavaScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Configurable replication on table/partition-level

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Read-after-write consistency on record level

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

Since BigQuery is designed for querying data

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.

User concepts

Access control

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

rights management via user accounts

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

Google Cloud Identity & Access Management (IAM)

More information provided by the system vendor

Specific characteristics

The enterprise database for time series, documents, and vectors. Distributed - Native...
» more

Competitive advantages

Response time in milliseconds: e ven for complex ad-hoc queries. Massive scaling...
» more

Typical application scenarios

IoT: accelerate your IIoT projects with CrateDB, delivering real-time analytics...
» more

Key customers

Across all continents, CrateDB is used by companies of all sizes to meet the most...
» more

Market metrics

The CrateDB open source project was started in 2013 Honorable Mention in 2021 Gartner®...
» more

Licensing and pricing models

See CrateDB pricing >
» 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.