DBMS > Apache Impala vs. Apache Kylin vs. Drizzle vs. Google BigQuery vs. IBM Cloudant

System Properties Comparison Apache Impala vs. Apache Kylin vs. Drizzle vs. Google BigQuery vs. IBM Cloudant

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

Analytic DBMS for Hadoop

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

Large scale data warehouse service with append-only tables

Database as a Service offering based on Apache CouchDB

Primary database model

Relational DBMS

Document store

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	1.25
Rank	#170	Overall
	#77	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Website

impala.apache.org

kylin.apache.org

cloud.google.com/bigquery

www.ibm.com/products/cloudant

Technical documentation

impala.apache.org/impala-docs.html

kylin.apache.org/docs

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation, originally contributed from eBay Inc

Drizzle project, originally started by Brian Aker

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Initial release

2013

2015

2008

2010

Current release

4.1.0, June 2022

3.1.0, July 2020

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

GNU GPL

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

Java

C++

Erlang

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Data scheme

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

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI SQL for queries (using Apache Calcite)

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

JDBC

RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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.

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Google Cloud Identity & Access Management (IAM)

Access rights for users can be defined per database

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.