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

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

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

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

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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.14
Rank	#344	Overall
	#32	Time Series DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

Technical documentation

www.exasol.com/resources

docs.snowflake.net/manuals/index.html

docs.stardog.com

www.warp10.io/content/02_Getting_started

yottadb.com/resources/documentation

Developer

Exasol

Snowflake Computing Inc.

Stardog-Union

SenX

YottaDB, LLC

Initial release

2000

2014

2010

2015

2001

Current release

7.3.0, May 2020

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

Apache License 2.0

Open Source

AGPL 3.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

Server operating systems

hosted

Linux
macOS
Windows

Linux
OS X
Windows

Docker
Linux

Data scheme

yes

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

schema-free and OWL/RDFS-schema support

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

by using the Octo plugin

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

HTTP API
Jupyter
WebSocket

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

Java
Lua
Python
R

JavaScript (Node.js)
Python

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

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

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

selectable replication factor

based on HBase

yes

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

optimistic locking

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

Users and groups based on OS-security mechanisms

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.