DBMS > Apache Druid vs. EsgynDB vs. Graphite vs. SQLite vs. ToroDB

System Properties Comparison Apache Druid vs. EsgynDB vs. Graphite vs. SQLite vs. ToroDB

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used embeddable, in-process RDBMS

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS
Time Series DBMS

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

Score	2.85
Rank	#96	Overall
	#50	Relational DBMS
	#6	Time Series DBMS

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

www.esgyn.cn

github.com/graphite-project/graphite-web

www.sqlite.org

github.com/torodb/server

Technical documentation

druid.apache.org/docs/latest/design

graphite.readthedocs.io

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

Esgyn

Chris Davis

Dwayne Richard Hipp

8Kdata

Initial release

2012

2015

2006

2000

2016

Current release

30.0.0, June 2024

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache license v2

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

AGPL-V3

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

Python

Java

Server operating systems

Linux
OS X
Unix

Linux

Linux
Unix

server-less

All OS with a Java 7 VM

Data scheme

yes

schema-less columns are supported

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

yes

string, integer, double, boolean, date, object_id

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.

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

HTTP API
Sockets

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

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication between multi datacenters

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

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

Access rights for 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.