DBMS > ArcadeDB vs. Drizzle vs. Riak TS vs. SAP HANA

System Properties Comparison ArcadeDB vs. Drizzle vs. Riak TS vs. SAP HANA

Please select another system to include it in the comparison.

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

Fast and scalable multi-model DBMS, originally forked from OrientDB but most of the code has been rewritten

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

Primary database model

Document store
Graph DBMS
Key-value store
Time Series DBMS

in next version

Relational DBMS

Time Series DBMS

Relational DBMS

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	0.02
Rank	#366	Overall
	#50	Document stores
	#38	Graph DBMS
	#53	Key-value stores
	#36	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

arcadedb.com

www.sap.com/products/hana.html

Technical documentation

docs.arcadedb.com

www.tiot.jp/riak-docs/riak/ts/latest

help.sap.com/hana

Developer

Arcade Data

Drizzle project, originally started by Brian Aker

Open Source, formerly Basho Technologies

SAP

Initial release

2021

2008

2015

2010

Current release

September 2021

7.2.4, September 2012

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

commercial

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

C++

Erlang

Server operating systems

All OS with a Java VM

FreeBSD
Linux
OS X

Linux
OS X

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

with proprietary extensions

yes, limited

yes

APIs and other access methods

JDBC
MongoDB API
OpenCypher
PostgreSQL wire protocol
Redis API
RESTful HTTP/JSON API
TinkerPop Gremlin

JDBC

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

Java

C
C++
Java
PHP

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

Erlang

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

links between datasets can be stored

yes

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

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.