DBMS > EXASOL vs. Snowflake vs. Stardog vs. WakandaDB vs. Warp 10

System Properties Comparison EXASOL vs. Snowflake vs. Stardog vs. WakandaDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

Technical documentation

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

docs.stardog.com

wakanda.github.io/doc

www.warp10.io/content/02_Getting_started

Developer

Exasol

Snowflake Computing Inc.

Stardog-Union

Wakanda SAS

SenX

Initial release

2000

2014

2010

2012

2015

Current release

7.3.0, May 2020

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

AGPLv3, extended commercial license available

Open Source

Apache License 2.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

C++, JavaScript

Java

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

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

schema-free and OWL/RDFS-schema support

yes

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

CLI Client
JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

RESTful HTTP API

HTTP API
Jupyter
WebSocket

Supported programming languages

Java
Lua
Python
R

JavaScript (Node.js)
Python

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

JavaScript

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

yes

WarpScript

Triggers

yes

similar concept for controling cloud resources

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in HA-Cluster

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

relationships in graphs

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 capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

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

Access rights for users and roles

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.