DBMS > Apache Druid vs. EsgynDB vs. Percona Server for MySQL vs. SQLite vs. SwayDB

System Properties Comparison Apache Druid vs. EsgynDB vs. Percona Server for MySQL vs. SQLite vs. SwayDB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Widely used embeddable, in-process RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS
Time Series DBMS

Relational DBMS

Key-value 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	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

druid.apache.org

www.esgyn.cn

www.percona.com/software/mysql-database/percona-server

www.sqlite.org

swaydb.simer.au

Technical documentation

druid.apache.org/docs/latest/design

www.percona.com/downloads/Percona-Server-LATEST

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

Esgyn

Percona

Dwayne Richard Hipp

Simer Plaha

Initial release

2012

2015

2008

2000

2018

Current release

29.0.1, April 2024

8.0.36-28, 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

GPL version 2

Open Source

Public Domain

Open Source

GNU Affero GPL V3.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.

Implementation language

Java

C++, Java

C and C++

Scala

Server operating systems

Linux
OS X
Unix

Linux

server-less

Data scheme

yes

schema-less columns are supported

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL for querying

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

All languages supporting JDBC/ODBC/ADO.Net

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication
XtraDB Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

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

fine grained access rights according to SQL-standard

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.