DBMS > Drizzle vs. Kdb vs. MySQL vs. NuoDB vs. Tarantool

System Properties Comparison Drizzle vs. Kdb vs. MySQL vs. NuoDB vs. Tarantool

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

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

High performance Time Series DBMS

Widely used open source RDBMS

NuoDB is a webscale distributed database that supports SQL and ACID transactions

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Time Series DBMS
Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	7.55
Rank	#53	Overall
	#3	Time Series DBMS
	#1	Vector DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

kx.com

www.mysql.com

www.3ds.com/nuodb-distributed-sql-database

www.tarantool.io

Technical documentation

code.kx.com

dev.mysql.com/doc

doc.nuodb.com

www.tarantool.io/en/doc

Developer

Drizzle project, originally started by Brian Aker

Kx Systems, a division of First Derivatives plc

Oracle

since 2010, originally MySQL AB, then Sun

Dassault Systèmes

originally NuoDB, Inc.

Initial release

2008

2000

kdb was released 2000, kdb+ in 2003

1995

2013

2008

Current release

7.2.4, September 2012

3.6, May 2018

8.4.0, April 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

free 32-bit version

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

limited edition free

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

C++

C and C++

Server operating systems

FreeBSD
Linux
OS X

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

BSD
Linux
macOS

Data scheme

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

table attribute 'grouped'

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language (q)

yes

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC

HTTP API
JDBC
Jupyter
Kafka
ODBC
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Open binary protocol

Supported programming languages

C
C++
Java
PHP

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

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

.Net
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Java, SQL

Lua, C and SQL stored procedures

Triggers

hooks for callbacks inside the server can be used.

yes

with views

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

data is dynamically stored/cached on the nodes where it is read/written

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication
Source-replica replication

yes

Managed transparently by NuoDB

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

similar paradigm used for internal processing

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

tunable commit protocol

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

MVCC

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

Temporary table

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

rights management via user accounts

Users with fine-grained authorization concept

no user groups or roles

Standard SQL roles/ privileges, Administrative Users

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.