DBMS > AnzoGraph DB vs. Datomic vs. Dgraph vs. RocksDB vs. Trafodion

System Properties Comparison AnzoGraph DB vs. Datomic vs. Dgraph vs. RocksDB 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

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Distributed and scalable native Graph DBMS

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

Transactional SQL-on-Hadoop DBMS

Primary database model

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

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

cambridgesemantics.com/anzograph

Technical documentation

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

docs.datomic.com

dgraph.io/docs

github.com/facebook/rocksdb/wiki

trafodion.apache.org/documentation.html

Developer

Cambridge Semantics

Cognitect

Dgraph Labs, Inc.

Facebook, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2018

2012

2016

2013

2014

Current release

2.3, January 2021

1.0.7075, December 2023

9.2.1, May 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

free trial version available

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

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

Java, Clojure

C++

C++, Java

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Windows

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

yes

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.

Secondary indexes

yes

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

APIs and other access methods

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

RESTful HTTP API

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

C++ API
Java API

ADO.NET
JDBC
ODBC

Supported programming languages

C++
Java
Python

Clojure
Java

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

C
C++
Go
Java
Perl
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Transaction Functions

Java Stored Procedures

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

But extensive use of caching in the application peers

yes

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication in MPP-Cluster

none

But extensive use of caching in the application peers

Synchronous replication via Raft

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency in MPP-Cluster

Immediate Consistency

Foreign keys

Referential integrity

not needed in graphs

yes

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

yes

User concepts

Access control

Access rights for users and roles

Planned for future releases

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.