DBMS > Datomic vs. Drizzle vs. RocksDB vs. SAP SQL Anywhere vs. Warp 10

System Properties Comparison Datomic vs. Drizzle vs. RocksDB vs. SAP SQL Anywhere vs. Warp 10

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle 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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

www.datomic.com

rocksdb.org

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

www.warp10.io

Technical documentation

docs.datomic.com

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

www.warp10.io/content/02_Getting_started

Developer

Cognitect

Drizzle project, originally started by Brian Aker

Facebook, Inc.

SAP

formerly Sybase

SenX

Initial release

2012

2008

2013

1992

2015

Current release

1.0.6735, June 2023

7.2.4, September 2012

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU GPL

Open Source

BSD

commercial

Open Source

Apache License 2.0

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

C++

Java

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

JDBC

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

Clojure
Java

C
C++
Java
PHP

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Transaction Functions

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

yes

WarpScript

Triggers

By using transaction functions

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

none

Sharding

based on HBase

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

yes

Source-replica replication

Database mirroring

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

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

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.