DBMS > Apache Drill vs. Drizzle vs. Google BigQuery vs. PostGIS vs. Rockset

System Properties Comparison Apache Drill vs. Drizzle vs. Google BigQuery vs. PostGIS vs. Rockset

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Large scale data warehouse service with append-only tables

Spatial extension of PostgreSQL

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store
Relational DBMS

Relational DBMS

Spatial DBMS

Document store

Secondary database models

Relational DBMS

Relational DBMS
Search engine

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Website

drill.apache.org

cloud.google.com/bigquery

postgis.net

rockset.com

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

postgis.net/documentation

docs.rockset.com

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Google

Rockset

Initial release

2012

2008

2010

2005

2019

Current release

1.20.3, January 2023

7.2.4, September 2012

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

commercial

Open Source

GPL v2.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

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

HTTP REST

Supported programming languages

C++

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

based on PostgreSQL

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Google Cloud Identity & Access Management (IAM)

yes

based on PostgreSQL

Access rights for users and organizations can be defined via Rockset console

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.