DBMS > Datomic vs. Graph Engine vs. SAP Adaptive Server vs. SQLite vs. TempoIQ

System Properties Comparison Datomic vs. Graph Engine vs. SAP Adaptive Server vs. SQLite vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Widely used embeddable, in-process RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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	35.09
Rank	#25	Overall
	#17	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.datomic.com

www.graphengine.io

www.sap.com/products/technology-platform/sybase-ase.html

www.sqlite.org

tempoiq.com (offline)

Technical documentation

docs.datomic.com

www.graphengine.io/docs/manual

help.sap.com/docs/SAP_ASE

www.sqlite.org/docs.html

Developer

Cognitect

Microsoft

SAP, Sybase

Dwayne Richard Hipp

TempoIQ

Initial release

2012

2010

1987

2000

2012

Current release

1.0.6735, June 2023

16.0

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

MIT License

commercial

Open Source

Public Domain

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

.NET and C

C and C++

Server operating systems

All OS with a Java VM

.NET

AIX
HP-UX
Linux
Solaris
Unix
Windows

server-less

Data scheme

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

Clojure
Java

C#
C++
F#
Visual Basic

C
C++
Cobol
Java
Java
Perl
PHP
Python

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Java and Transact-SQL

Triggers

By using transaction functions

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

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

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

fine grained access rights according to SQL-standard

simple authentication-based access control

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.