DBMS > Dgraph vs. Heroic vs. Microsoft Azure Cosmos DB vs. STSdb vs. Trafodion

System Properties Comparison Dgraph vs. Heroic vs. Microsoft Azure Cosmos DB vs. STSdb vs. Trafodion

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Globally distributed, horizontally scalable, multi-model database service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Transactional SQL-on-Hadoop DBMS

Primary database model

Graph DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

dgraph.io

github.com/spotify/heroic

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

trafodion.apache.org

Technical documentation

dgraph.io/docs

spotify.github.io/heroic

learn.microsoft.com/azure/cosmos-db

trafodion.apache.org/documentation.html

Developer

Dgraph Labs, Inc.

Spotify

Microsoft

STS Soft SC

Apache Software Foundation, originally developed by HP

Initial release

2016

2014

2011

2014

Current release

4.0.8, September 2015

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

commercial

Open Source

GPLv2, commercial license available

Open Source

Apache 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++, Java

Server operating systems

Linux
OS X
Windows

hosted

Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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.

Secondary indexes

yes

via Elasticsearch

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API

ADO.NET
JDBC
ODBC

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

JavaScript

Java Stored Procedures

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Implicit feature of the cloud service

none

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

Planned for future releases

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.