DBMS > Datomic vs. Graphite vs. Quasardb vs. RocksDB vs. SAP Advantage Database Server

System Properties Comparison Datomic vs. Graphite vs. Quasardb vs. RocksDB vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Distributed, high-performance timeseries database

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.datomic.com

github.com/graphite-project/graphite-web

quasar.ai

rocksdb.org

www.sap.com/products/advantage-database-server.html

Technical documentation

docs.datomic.com

graphite.readthedocs.io

doc.quasar.ai/master

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Chris Davis

quasardb

Facebook, Inc.

Sybase, SAP

Initial release

2012

2006

2009

2013

1993

Current release

1.0.7075, December 2023

3.14.1, January 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

Python

C++

Server operating systems

All OS with a Java VM

Linux
Unix

BSD
Linux
OS X
Windows

Linux

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

yes

integer and binary

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

with tags

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

HTTP API
Sockets

HTTP API

C++ API
Java API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Clojure
Java

JavaScript (Node.js)
Python

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

C
C++
Go
Java
Perl
Python
Ruby

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

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

none

Sharding

consistent hashing

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

Source-replica replication with selectable replication factor

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

by using LevelDB

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

Transient mode

yes

caching of (temporary) tables can be configured

User concepts

Access control

Cryptographically strong user authentication and audit trail

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.