DBMS > Apache Druid vs. Microsoft Azure Synapse Analytics vs. MySQL vs. Oracle Coherence vs. Tarantool

System Properties Comparison Apache Druid vs. Microsoft Azure Synapse Analytics vs. MySQL vs. Oracle Coherence vs. Tarantool

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Widely used open source RDBMS

Oracles in-memory data grid solution

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

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Key-value store

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

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

Website

druid.apache.org

azure.microsoft.com/services/synapse-analytics

www.mysql.com

www.oracle.com/java/coherence

www.tarantool.io

Technical documentation

druid.apache.org/docs/latest/design

docs.microsoft.com/azure/synapse-analytics

dev.mysql.com/doc

docs.oracle.com/en/middleware/standalone/coherence

www.tarantool.io/en/doc

Developer

Apache Software Foundation and contributors

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2012

2016

1995

2007

2008

Current release

29.0.1, April 2024

8.4.0, April 2024

14.1, August 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

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

Cloud-based only

Only available as a cloud service

yes

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

Java

C++

C and C++

Java

C and C++

Server operating systems

Linux
OS X
Unix

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

BSD
Linux
macOS

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

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

SQL

Support of SQL

SQL for querying

yes

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JCache
JPA
RESTful HTTP API

Open binary protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
Java
PHP

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

.Net
C++
Java

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

Server-side scripts

Stored procedures

Transact SQL

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

yes

Live Events

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding, horizontal partitioning

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.

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

Multi-source replication
Source-replica replication

yes, with selectable consistency level

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

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

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

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

configurable

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

yes, cooperative multitasking

Durability

Support for making data persistent

yes

optionally

yes, write ahead logging

In-memory capabilities

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

yes

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

yes

Users with fine-grained authorization concept

no user groups or roles

authentification to access the cache via certificates or http basic authentication

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

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.