DBMS > CockroachDB vs. Datomic vs. Dgraph vs. EsgynDB vs. SAP HANA

System Properties Comparison CockroachDB vs. Datomic vs. Dgraph vs. EsgynDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Graph DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.cockroachlabs.com

www.datomic.com

dgraph.io

www.esgyn.cn

www.sap.com/products/hana.html

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

dgraph.io/docs

help.sap.com/hana

Developer

Cockroach Labs

Cognitect

Dgraph Labs, Inc.

Esgyn

SAP

Initial release

2015

2012

2016

2015

2010

Current release

24.1.0, May 2024

1.0.7075, December 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

C++, Java

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

Linux
OS X
Windows

Linux

Appliance or cloud-service

Data scheme

dynamic schema

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

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

JDBC

RESTful HTTP API

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

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

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

Clojure
Java

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Transaction Functions

Java Stored Procedures

SQLScript, R

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

But extensive use of caching in the application peers

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

Role-based access control

Planned for future releases

fine grained access rights according to SQL-standard

yes

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.