DBMS > AgensGraph vs. Oracle Berkeley DB vs. Riak KV vs. SAP HANA vs. STSdb

System Properties Comparison AgensGraph vs. Oracle Berkeley DB vs. Riak KV vs. SAP HANA vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Graph DBMS
Relational DBMS

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

Key-value store

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.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

bitnine.net/agensgraph

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

www.sap.com/products/hana.html

github.com/STSSoft/STSdb4

Technical documentation

bitnine.net/documentation

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

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

help.sap.com/hana

Developer

Bitnine Global Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

OpenSource, formerly Basho Technologies

SAP

STS Soft SC

Initial release

2016

1994

2009

2010

2011

Current release

2.1, December 2018

18.1.40, May 2020

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial license available

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

GPLv2, commercial license available

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

Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X

Appliance or cloud-service

Windows

Data scheme

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

Cypher Query Language
JDBC

HTTP API
Native Erlang Interface

JDBC
ODBC

.NET Client API

Supported programming languages

C
Java
JavaScript
Python

.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#
Java

Server-side scripts

Stored procedures

yes

Erlang

SQLScript, R

Triggers

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

no, but can be realized using table inheritance

none

Sharding

no "single point of failure"

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

yes

none

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 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

fine grained access rights according to SQL-standard

yes, using Riak Security

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.