DBMS > Apache Druid vs. Dgraph vs. EsgynDB vs. LokiJS vs. SQLite

System Properties Comparison Apache Druid vs. Dgraph vs. EsgynDB vs. LokiJS vs. SQLite

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

Distributed and scalable native Graph DBMS

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

In-memory JavaScript DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS
Time Series DBMS

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	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

druid.apache.org

dgraph.io

www.esgyn.cn

github.com/techfort/LokiJS

www.sqlite.org

Technical documentation

druid.apache.org/docs/latest/design

dgraph.io/docs

techfort.github.io/LokiJS

www.sqlite.org/docs.html

Developer

Apache Software Foundation and contributors

Dgraph Labs, Inc.

Esgyn

Dwayne Richard Hipp

Initial release

2012

2016

2015

2014

2000

Current release

29.0.1, April 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

JavaScript

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

yes

schema-less columns are supported

schema-free

yes

schema-free

yes

dynamic column types

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.

Secondary indexes

yes

via views

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

ADO.NET
JDBC
ODBC

JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

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

All languages supporting JDBC/ODBC/ADO.Net

JavaScript

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

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Synchronous replication via Raft

Multi-source replication between multi datacenters

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single collection possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Planned for future releases

fine grained access rights according to SQL-standard

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.