DBMS > Apache Drill vs. Google BigQuery vs. Heroic vs. IBM Db2 vs. Memcached

System Properties Comparison Apache Drill vs. Google BigQuery vs. Heroic vs. IBM Db2 vs. Memcached

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Common in IBM host environments, 2 different versions for host and Windows/Linux

In-memory key-value store, originally intended for caching

Primary database model

Document store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Website

drill.apache.org

cloud.google.com/bigquery

github.com/spotify/heroic

www.ibm.com/products/db2

www.memcached.org

Technical documentation

drill.apache.org/docs

cloud.google.com/bigquery/docs

spotify.github.io/heroic

www.ibm.com/docs/en/db2

github.com/memcached/memcached/wiki

Developer

Apache Software Foundation

Google

Spotify

IBM

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Initial release

2012

2010

2014

1983

host version

2003

Current release

1.20.3, January 2023

12.1, October 2016

1.6.27, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

Apache 2.0

commercial

free version is available

Open Source

BSD license

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 and C++

Server operating systems

Linux
OS X
Windows

hosted

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Unix
Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free

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

via Elasticsearch

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Proprietary protocol

Supported programming languages

C++

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

only with Windows/Unix/Linux Version

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Repcached, a Memcached patch, provides this functionallity

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
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

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

yes

using SASL (Simple Authentication and Security Layer) protocol

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.