DBMS > Apache Druid vs. MySQL vs. Percona Server for MongoDB vs. Tarantool vs. YugabyteDB

System Properties Comparison Apache Druid vs. MySQL vs. Percona Server for MongoDB vs. Tarantool vs. YugabyteDB

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

Widely used open source RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

Document store
Wide column store

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Score	2.63
Rank	#109	Overall
	#53	Relational DBMS

Website

druid.apache.org

www.mysql.com

www.percona.com/mongodb/software/percona-server-for-mongodb

www.tarantool.io

www.yugabyte.com

Technical documentation

druid.apache.org/docs/latest/design

dev.mysql.com/doc

docs.percona.com/percona-distribution-for-mongodb

www.tarantool.io/en/doc

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

Apache Software Foundation and contributors

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Yugabyte Inc.

Initial release

2012

1995

2015

2008

2017

Current release

29.0.1, April 2024

8.4.0, April 2024

3.4.10-2.10, November 2017

2.10.0, May 2022

2.19, September 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL Version 2

Open Source

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

Open Source

Apache 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.

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

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

Java

C and C++

C++

C and C++

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
macOS

Linux
OS X

Data scheme

yes

schema-less columns are supported

yes

schema-free

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

depending on used data model

Typing

predefined data types such as float or date

yes

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

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

SQL

Support of SQL

SQL for querying

yes

with proprietary extensions

Full-featured ANSI SQL support

yes, PostgreSQL compatible

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Open binary protocol

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

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

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

Lua, C and SQL stored procedures

yes

sql, plpgsql, C

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication
Source-replica replication

Source-replica replication

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

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

Strong consistency on writes and tunable consistency on reads

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, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

based on RocksDB

In-memory capabilities

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

yes

via In-Memory Engine

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

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

yes

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» 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.