DBMS > Datomic vs. Dgraph vs. Hazelcast vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Datomic vs. Dgraph vs. Hazelcast vs. RocksDB vs. SAP SQL Anywhere

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

A widely adopted in-memory data grid

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Website

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.datomic.com

dgraph.io/docs

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Cognitect

Dgraph Labs, Inc.

Hazelcast

Facebook, Inc.

SAP

formerly Sybase

Initial release

2012

2016

2008

2013

1992

Current release

1.0.6735, June 2023

5.3.6, November 2023

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

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

Java

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

All OS with a Java VM

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

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.

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

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

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

Clojure
Java

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Event Listeners, Executor Services

yes, in C/C++, Java, .Net or Perl

Triggers

By using transaction functions

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

yes

Sharding

horizontal partitioning

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

Replicated Map

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

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

Planned for future releases

Role-based access control

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.