DBMS > Datomic vs. Graph Engine vs. IBM Db2 warehouse vs. SAP SQL Anywhere vs. SQLite

System Properties Comparison Datomic vs. Graph Engine vs. IBM Db2 warehouse vs. SAP SQL Anywhere vs. SQLite

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

Cloud-based data warehousing service

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

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

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.34
Rank	#166	Overall
	#76	Relational DBMS

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.datomic.com

www.graphengine.io

www.ibm.com/products/db2/warehouse

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

www.sqlite.org

Technical documentation

docs.datomic.com

www.graphengine.io/docs/manual

help.sap.com/docs/SAP_SQL_Anywhere

www.sqlite.org/docs.html

Developer

Cognitect

Microsoft

IBM

SAP

formerly Sybase

Dwayne Richard Hipp

Initial release

2012

2010

2014

1992

2000

Current release

1.0.6735, June 2023

17, July 2015

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

MIT License

commercial

Open Source

Public Domain

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

.NET and C

Server operating systems

All OS with a Java VM

.NET

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
OLE DB

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
Java

C#
C++
F#
Visual Basic

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

PL/SQL, SQL PL

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

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes

Source-replica replication

Database mirroring

none

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

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

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.