DBMS > EXASOL vs. OrientDB vs. Snowflake vs. Teradata vs. TigerGraph

System Properties Comparison EXASOL vs. OrientDB vs. Snowflake vs. Teradata vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

Multi-model DBMS (Document, Graph, Key/Value)

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

A hybrid cloud data analytics software platform (Teradata Vantage)

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	3.25
Rank	#89	Overall
	#16	Document stores
	#6	Graph DBMS
	#13	Key-value stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	44.87
Rank	#22	Overall
	#15	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

Technical documentation

www.exasol.com/resources

www.orientdb.com/docs/last/index.html

docs.snowflake.net/manuals/index.html

docs.teradata.com

docs.tigergraph.com

Developer

Exasol

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Teradata

Initial release

2000

2010

2014

1984

2017

Current release

3.2.29, March 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

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++

Server operating systems

All OS with a Java JDK (>= JDK 6)

hosted

hosted
Linux

Linux

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

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

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL-like query language, no joins

yes

SQL 2016 + extensions

SQL-like query language (GSQL)

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

Java
Lua
Python
R

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

Java, Javascript

user defined functions

yes

UDFs, stored procedures, table functions in parallel

yes

Triggers

yes

Hooks

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

could be achieved with distributed queries

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

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

Access rights for users and roles; record level security configurable

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

fine grained access rights according to SQL-standard

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.