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

System Properties Comparison Drizzle vs. Immudb 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

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

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

Secondary database models

Relational DBMS

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.31
Rank	#295	Overall
	#42	Key-value stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

github.com/codenotary/immudb
immudb.io

www.sap.com/products/hana.html

Technical documentation

docs.immudb.io

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

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

Codenotary

Open Source, formerly Basho Technologies

SAP

Initial release

2008

2020

2015

2010

Current release

7.2.4, September 2012

1.2.3, April 2022

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2.0

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

C++

Erlang

Server operating systems

FreeBSD
Linux
OS X

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux
OS X

Appliance or cloud-service

Data scheme

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

yes

with proprietary extensions

SQL-like syntax

yes, limited

yes

APIs and other access methods

JDBC

gRPC protocol
PostgreSQL wire protocol

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

C
C++
Java
PHP

.Net
Go
Java
JavaScript (Node.js)
Python

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

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

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.