DBMS > Apache Drill vs. Firebolt vs. Google BigQuery vs. Greenplum vs. InfinityDB

System Properties Comparison Apache Drill vs. Firebolt vs. Google BigQuery vs. Greenplum vs. InfinityDB

Editorial information provided by DB-Engines

Name

Description

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

Highly scalable cloud data warehouse and analytics product

Forked from Clickhouse

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 Java embedded Key-Value Store which extends the Java Map interface

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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	1.73
Rank	#140	Overall
	#63	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Website

drill.apache.org

www.firebolt.io

cloud.google.com/bigquery

greenplum.org

boilerbay.com

Technical documentation

drill.apache.org/docs

docs.firebolt.io

cloud.google.com/bigquery/docs

docs.greenplum.org

boilerbay.com/infinitydb/manual

Developer

Apache Software Foundation

Firebolt Analytics Inc.

Google

Pivotal Software Inc.

Boiler Bay Inc.

Initial release

2012

2020

2010

2005

2002

Current release

1.20.3, January 2023

7.0.0, September 2023

4.0

License

Commercial or Open Source

Open Source

Apache Version 2

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
Windows

hosted

Linux

All OS with a Java VM

Data scheme

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.Net
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

Supported programming languages

C++

Go
JavaScript (Node.js)
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

READ-COMMITTED or SERIALIZED

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

Since BigQuery is designed for querying data

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

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

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.