DBMS > AnzoGraph DB vs. Datomic vs. MySQL vs. RocksDB

System Properties Comparison AnzoGraph DB vs. Datomic vs. MySQL vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Widely used open source RDBMS

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

Primary database model

Graph DBMS
RDF store

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.23
Rank	#307	Overall
	#24	Graph DBMS
	#13	RDF stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

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

Website

cambridgesemantics.com/anzograph

www.datomic.com

www.mysql.com

rocksdb.org

Technical documentation

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

docs.datomic.com

dev.mysql.com/doc

github.com/facebook/rocksdb/wiki

Developer

Cambridge Semantics

Cognitect

Oracle

since 2010, originally MySQL AB, then Sun

Facebook, Inc.

Initial release

2018

2012

1995

2013

Current release

2.3, January 2021

1.0.6735, June 2023

8.4.0, April 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

free trial version available

commercial

limited edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java, Clojure

C and C++

C++

Server operating systems

Linux

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Schema-free and OWL/RDFS-schema support

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

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

APIs and other access methods

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

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

C++ API
Java API

Supported programming languages

C++
Java
Python

Clojure
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

Transaction Functions

yes

proprietary syntax

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

But extensive use of caching in the application peers

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

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

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Kerberos/HDFS data loading

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

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

yes

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.