DBMS > Datomic vs. Graph Engine vs. SAP HANA vs. Stardog

System Properties Comparison Datomic vs. Graph Engine vs. SAP HANA vs. Stardog

Please select another system to include it in the comparison.

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Graph DBMS
RDF store

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	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

www.datomic.com

www.graphengine.io

www.sap.com/products/hana.html

www.stardog.com

Technical documentation

docs.datomic.com

www.graphengine.io/docs/manual

help.sap.com/hana

docs.stardog.com

Developer

Cognitect

Microsoft

SAP

Stardog-Union

Initial release

2012

2010

Current release

1.0.7075, December 2023

2.0 SPS07 (April 4, 2023), April 2023

7.3.0, May 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

MIT License

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

.NET and C

Java

Server operating systems

All OS with a Java VM

.NET

Appliance or cloud-service

Linux
macOS
Windows

Data scheme

yes

schema-free and OWL/RDFS-schema support

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

Clojure
Java

C#
C++
F#
Visual Basic

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

SQLScript, R

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

By using transaction functions

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

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)

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

yes

Access rights for users and 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.