DBMS > Amazon Neptune vs. Apache Drill vs. Snowflake vs. SwayDB vs. TerminusDB

System Properties Comparison Amazon Neptune vs. Apache Drill vs. Snowflake vs. SwayDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

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

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

Graph DBMS
RDF store

Document store
Relational DBMS

Relational DBMS

Key-value store

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	2.29
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

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

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

aws.amazon.com/neptune

Technical documentation

aws.amazon.com/neptune/developer-resources

drill.apache.org/docs

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Amazon

Apache Software Foundation

Snowflake Computing Inc.

Simer Plaha

DataChemist Ltd.

Initial release

2017

2012

2014

2018

Current release

1.20.3, January 2023

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

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

Scala

Prolog, Rust

Server operating systems

hosted

Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

yes

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

schema-free

yes

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

SQL-like query language (WOQL)

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

C++

JavaScript (Node.js)
Python

Java
Kotlin
Scala

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

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

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 execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with encyption-at-rest

Depending on the underlying data source

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Depending on the underlying data source

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.