DBMS > Snowflake vs. TerarkDB vs. TigerGraph vs. Titan

System Properties Comparison Snowflake vs. TerarkDB vs. TigerGraph vs. Titan

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

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

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Key-value store

Graph DBMS

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Website

www.snowflake.com

github.com/bytedance/terarkdb

www.tigergraph.com

github.com/thinkaurelius/titan

Technical documentation

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.tigergraph.com

github.com/thinkaurelius/titan/wiki

Developer

Snowflake Computing Inc.

ByteDance, originally Terark

Aurelius, owned by DataStax

Initial release

2014

2016

2017

2012

License

Commercial or Open Source

commercial

restricted open source version available

commercial

Open Source

Apache license, version 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

C++

Java

Server operating systems

hosted

Linux

Linux
OS X
Unix
Windows

Data scheme

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

yes

SQL

Support of SQL

yes

SQL-like query language (GSQL)

APIs and other access methods

CLI Client
JDBC
ODBC

C++ API
Java API

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

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

JavaScript (Node.js)
Python

C++
Java

Clojure
Java
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

yes

none

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graph

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

In-memory capabilities

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

yes

User concepts

Access control

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

Role-based access control

User authentification and security via Rexster Graph Server

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.