DBMS > Apache Drill vs. CouchDB vs. Google BigQuery vs. Kdb

System Properties Comparison Apache Drill vs. CouchDB vs. Google BigQuery vs. Kdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Large scale data warehouse service with append-only tables

High performance Time Series DBMS

Primary database model

Document store
Relational DBMS

Document store

Relational DBMS

Time Series DBMS
Vector DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	52.67
Rank	#19	Overall
	#13	Relational DBMS

Score	7.73
Rank	#45	Overall
	#2	Time Series DBMS
	#1	Vector DBMS

Website

drill.apache.org

couchdb.apache.org

cloud.google.com/bigquery

kx.com

Technical documentation

drill.apache.org/docs

docs.couchdb.org/en/stable

cloud.google.com/bigquery/docs

code.kx.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Google

Kx Systems, a division of First Derivatives plc

Initial release

2012

2005

2010

2000

kdb was released 2000, kdb+ in 2003

Current release

1.20.3, January 2023

3.3.3, December 2023

3.6, May 2018

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

commercial

free 32-bit version

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

Erlang

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

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.

yes

Secondary indexes

yes

via views

yes

table attribute 'grouped'

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language (q)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

Supported programming languages

C++

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
C#
C++
Go
J
Java
JavaScript
Lua
MatLab
Perl
PHP
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

user defined functions

in JavaScript

user defined functions

Triggers

yes

with views

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

yes

User concepts

Access control

Depending on the underlying data source

Access rights for users can be defined per database

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

Google Cloud Identity & Access Management (IAM)

rights management via user accounts

More information provided by the system vendor

Specific characteristics

Integrated columnar database & programming system for streaming, real time and historical...
» more

Competitive advantages

provides seamless scalability; runs on industry standard server platforms; is top-ranked...
» more

Typical application scenarios

tick database streaming sensor data massive intelligence applications oil and gas...
» more

Key customers

Goldman Sachs Morgan Stanley Merrill Lynch J.P. Morgan Deutsche Bank IEX Securities...
» more

Market metrics

kdb+ performance and reliability proven by our customers in critical infrastructure...
» more

Licensing and pricing models

upon request
» 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.