DBMS > Datomic vs. Dgraph vs. RocksDB vs. TDSQL for MySQL vs. UniData,UniVerse

System Properties Comparison Datomic vs. Dgraph vs. RocksDB vs. TDSQL for MySQL vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

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)

A high-performance distributed database management system with features such as automatic sharding, intelligent operation and maintenance, elastic scalability without downtime, and enterprise-grade security. It is highly compatible with MySQL.

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store
Spatial DBMS

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

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

Score	0.85
Rank	#207	Overall
	#97	Relational DBMS

Score	2.85
Rank	#98	Overall
	#1	Multivalue DBMS

Website

www.datomic.com

dgraph.io

rocksdb.org

www.tencentcloud.com/products/dcdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

docs.datomic.com

dgraph.io/docs

github.com/facebook/rocksdb/wiki

www.tencentcloud.com/document/product/1042

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

Cognitect

Dgraph Labs, Inc.

Facebook, Inc.

Tencent

Rocket Software

Initial release

2012

2016

2013

1985

Current release

1.0.7075, December 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

commercial

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

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

yes

APIs and other access methods

RESTful HTTP API

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

C++ API
Java API

JDBC
ODBC

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

Clojure
Java

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

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
PHP
Python
Ruby

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

horizontal partitioning

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Synchronous replication via Raft

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

ACID

configurable

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

Planned for future releases

Users with fine-grained authorization concept

Access rights according to SQL-standard and operating system based

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.