DBMS > Apache Drill vs. JanusGraph vs. LokiJS vs. Snowflake vs. SwayDB

System Properties Comparison Apache Drill vs. JanusGraph vs. LokiJS vs. Snowflake vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

In-memory JavaScript DBMS

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Document store
Relational DBMS

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

drill.apache.org

janusgraph.org

github.com/techfort/LokiJS

www.snowflake.com

swaydb.simer.au

Technical documentation

drill.apache.org/docs

docs.janusgraph.org

techfort.github.io/LokiJS

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Linux Foundation; originally developed as Titan by Aurelius

Snowflake Computing Inc.

Simer Plaha

Initial release

2012

2017

2014

2018

Current release

1.20.3, January 2023

0.6.3, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

Open Source

commercial

Open Source

GNU Affero GPL V3.0

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.

Implementation language

Java

JavaScript

Scala

Server operating systems

Linux
OS X
Windows

Linux
OS X
Unix
Windows

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

hosted

Data scheme

schema-free

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

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

via views

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

C++

Clojure
Java
Python

JavaScript

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

yes

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

atomic operations within a single collection possible

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept, user roles and pluggable authentication

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.