DBMS > Amazon Redshift vs. ArcadeDB vs. Snowflake vs. TerminusDB vs. WakandaDB

System Properties Comparison Amazon Redshift vs. ArcadeDB vs. Snowflake vs. TerminusDB vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

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

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Graph DBMS

Object oriented DBMS

Secondary database models

Document store
RDF store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.10
Rank	#358	Overall
	#48	Document stores
	#38	Graph DBMS
	#52	Key-value stores
	#35	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

docs.arcadedb.com

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Arcade Data

Snowflake Computing Inc.

DataChemist Ltd.

Wakanda SAS

Initial release

2012

2021

2014

2018

2012

Current release

September 2021

11.0.0, January 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

GPL V3

Open Source

AGPLv3, extended commercial license available

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

Prolog, Rust

C++, JavaScript

Server operating systems

hosted

All OS with a Java VM

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language, no joins

yes

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Java

JavaScript (Node.js)
Python

JavaScript
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

Triggers

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Journaling Streams

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationship in graphs

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

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

Role-based access control

yes

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.