DBMS > Drizzle vs. RocksDB vs. Teradata Aster vs. TigerGraph vs. TinkerGraph

System Properties Comparison Drizzle vs. RocksDB vs. Teradata Aster vs. TigerGraph vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Platform for big data analytics on multistructured data sources and types

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

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

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	1.83
Rank	#139	Overall
	#13	Graph DBMS

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

rocksdb.org

www.tigergraph.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

github.com/facebook/rocksdb/wiki

docs.tigergraph.com

Developer

Drizzle project, originally started by Brian Aker

Facebook, Inc.

Teradata

Initial release

2008

2013

2005

2017

2009

Current release

7.2.4, September 2012

8.11.4, April 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSD

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

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

FreeBSD
Linux
OS X

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (GSQL)

APIs and other access methods

JDBC

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

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

TinkerPop 3

Supported programming languages

C
C++
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

C++
Java

Groovy
Java

Server-side scripts

Stored procedures

R packages

yes

Triggers

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

none

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Relationships in graphs

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

In-memory capabilities

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.