DBMS > Apache Drill vs. HarperDB vs. Snowflake vs. SwayDB vs. TerminusDB

System Properties Comparison Apache Drill vs. HarperDB vs. Snowflake vs. SwayDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Relational DBMS

Secondary database models

Document store
RDF store

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

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

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

Technical documentation

drill.apache.org/docs

docs.harperdb.io/docs

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Apache Software Foundation

HarperDB

Snowflake Computing Inc.

Simer Plaha

DataChemist Ltd.

Initial release

2012

2017

2014

2018

Current release

1.20.3, January 2023

3.1, August 2021

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free community edition available

commercial

Open Source

GNU Affero GPL V3.0

Open Source

GPL V3

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

Node.js

Scala

Prolog, Rust

Server operating systems

Linux
OS X
Windows

Linux
OS X

hosted

Linux

Data scheme

schema-free

dynamic schema

yes

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

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON data types

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like data manipulation statements

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C++

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

JavaScript (Node.js)
Python

Java
Kotlin
Scala

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

Custom Functions

since release 3.1

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

A table resides as a whole on one (or more) nodes in a cluster

yes

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes, using LMDB

yes

in-memory journaling

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

Access rights for users and roles

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

Role-based access control

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.