DBMS > Apache Druid vs. Google BigQuery vs. Greenplum vs. LeanXcale vs. PlanetScale

System Properties Comparison Apache Druid vs. Google BigQuery vs. Greenplum vs. LeanXcale vs. PlanetScale

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Scalable, distributed, serverless MySQL database platform built on top of Vitess

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	0.29
Rank	#291	Overall
	#41	Key-value stores
	#132	Relational DBMS

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

druid.apache.org

cloud.google.com/bigquery

greenplum.org

www.leanxcale.com

planetscale.com

Technical documentation

druid.apache.org/docs/latest/design

cloud.google.com/bigquery/docs

docs.greenplum.org

planetscale.com/docs

Developer

Apache Software Foundation and contributors

Google

Pivotal Software Inc.

LeanXcale

PlanetScale

Initial release

2012

2010

2005

2015

2020

Current release

29.0.1, April 2024

7.0.0, September 2023

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache 2.0

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

Server operating systems

Linux
OS X
Unix

hosted

Linux

Docker
Linux
macOS

Data scheme

yes

schema-less columns are supported

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.

yes

since Version 4.2

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

through Apache Derby

yes

with proprietary extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

RESTful HTTP/JSON API

JDBC
ODBC

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

C
Java
Scala

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

proprietary syntax

Triggers

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

Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.