DBMS > Apache Drill vs. Bangdb vs. Drizzle vs. SQLite

System Properties Comparison Apache Drill vs. Bangdb vs. Drizzle vs. SQLite

Please select another system to include it in the comparison.

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

Converged and high performance database for device data, events, time series, document and graph

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

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Secondary database models

Spatial 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	0.07
Rank	#346	Overall
	#47	Document stores
	#35	Graph DBMS
	#32	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

bangdb.com

www.sqlite.org

Technical documentation

drill.apache.org/docs

docs.bangdb.com

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Sachin Sinha, BangDB

Drizzle project, originally started by Brian Aker

Dwayne Richard Hipp

Initial release

2012

2008

2000

Current release

1.20.3, January 2023

BangDB 2.0, October 2021

7.2.4, September 2012

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

BSD 3

Open Source

GNU GPL

Open Source

Public Domain

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

C++

Server operating systems

Linux
OS X
Windows

Linux

FreeBSD
Linux
OS X

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes: string, long, double, int, geospatial, stream, events

yes

not rigid because of 'dynamic typing' concept.

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL like support with command line tool

yes

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol
RESTful HTTP API

JDBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

C
C#
C++
Java
Python

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

Server-side scripts

Stored procedures

user defined functions

Triggers

yes, Notifications (with Streaming only)

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication
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

Tunable consistency, set CAP knob accordingly

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

yes, optimistic concurrency control

yes

via file-system locks

Durability

Support for making data persistent

Depending on the underlying data source

yes, implements WAL (Write ahead log) as well

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, run db with in-memory only mode

yes

User concepts

Access control

Depending on the underlying data source

yes (enterprise version only)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.