DBMS > etcd vs. Oracle Berkeley DB vs. Riak KV vs. SAP HANA vs. SAP SQL Anywhere

System Properties Comparison etcd vs. Oracle Berkeley DB vs. Riak KV vs. SAP HANA vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Widely used in-process key-value store

Distributed, fault tolerant key-value store

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

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

Primary database model

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

etcd.io
github.com/etcd-io/etcd

www.oracle.com/database/technologies/related/berkeleydb.html

www.sap.com/products/hana.html

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

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.oracle.com/cd/E17076_05/html/index.html

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

help.sap.com/hana

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OpenSource, formerly Basho Technologies

SAP

formerly Sybase

Initial release

1994

2009

2010

1992

Current release

3.4, August 2019

18.1.40, May 2020

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

17, July 2015

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

commercial license available

Open Source

Apache version 2, commercial enterprise edition

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, Java, C++ (depending on the Berkeley DB edition)

Erlang

Server operating systems

FreeBSD
Linux
Windows

experimental

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Appliance or cloud-service

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

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.

yes

only with the Berkeley DB XML edition

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

gRPC
JSON over HTTP

HTTP API
Native Erlang Interface

JDBC
ODBC

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

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

Server-side scripts

Stored procedures

Erlang

SQLScript, R

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

Triggers

yes, watching key changes

yes

only for the SQL API

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Source-replica replication

selectable replication factor

yes

Source-replica replication

Database mirroring

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

links between data sets 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

yes, using Riak Security

yes

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.