DBMS > Apache Druid vs. Bangdb vs. MySQL

System Properties Comparison Apache Druid vs. Bangdb vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Widely used open source RDBMS

Primary database model

Relational DBMS
Time Series DBMS

Document store
Graph DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	2.94
Rank	#93	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	0.09
Rank	#343	Overall
	#47	Document stores
	#34	Graph DBMS
	#30	Time Series DBMS

Score	1039.46
Rank	#2	Overall
	#2	Relational DBMS

Website

druid.apache.org

bangdb.com

www.mysql.com

Technical documentation

druid.apache.org/docs/latest/design

docs.bangdb.com

dev.mysql.com/doc

Developer

Apache Software Foundation and contributors

Sachin Sinha, BangDB

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

1995

Current release

30.0.0, June 2024

BangDB 2.0, October 2021

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD 3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C, C++

C and C++

Server operating systems

Linux
OS X
Unix

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

Typing

predefined data types such as float or date

yes

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

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL for querying

SQL like support with command line tool

yes

with proprietary extensions

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Proprietary protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C#
C++
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes, Notifications (with Streaming only)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

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

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, optimistic concurrency control

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

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.

yes, run db with in-memory only mode

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

yes (enterprise version only)

Users with fine-grained authorization concept

no user groups or roles

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.