DBMS > Apache Drill vs. Drizzle vs. SQLite vs. TerarkDB vs. Warp 10

System Properties Comparison Apache Drill vs. Drizzle vs. SQLite vs. TerarkDB vs. Warp 10

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.

Widely used embeddable, in-process RDBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

Time Series DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

drill.apache.org

www.sqlite.org

github.com/bytedance/terarkdb

www.warp10.io

Technical documentation

drill.apache.org/docs

www.sqlite.org/docs.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

www.warp10.io/content/02_Getting_started

Developer

Apache Software Foundation

Drizzle project, originally started by Brian Aker

Dwayne Richard Hipp

ByteDance, originally Terark

SenX

Initial release

2012

2008

2000

2016

2015

Current release

1.20.3, January 2023

7.2.4, September 2012

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GNU GPL

Open Source

Public Domain

commercial

restricted open source version available

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X

server-less

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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 SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

C++

C
C++
Java
PHP

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes

WarpScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.