DBMS > Riak KV vs. SAP HANA vs. Sphinx vs. TerminusDB

System Properties Comparison Riak KV vs. SAP HANA vs. Sphinx vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed, fault tolerant key-value store

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

Open source search engine for searching in data from different sources, e.g. relational databases

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

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

Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Document store
RDF store

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

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.sap.com/products/hana.html

sphinxsearch.com

terminusdb.com

Technical documentation

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

help.sap.com/hana

sphinxsearch.com/docs

terminusdb.github.io/terminusdb/#

Developer

OpenSource, formerly Basho Technologies

SAP

Sphinx Technologies Inc.

DataChemist Ltd.

Initial release

2009

2010

2001

2018

Current release

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPL V3

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

Erlang

C++

Prolog, Rust

Server operating systems

Linux
OS X

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

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.

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

SQL-like query language (WOQL)

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript
Python

Server-side scripts

Stored procedures

Erlang

SQLScript, R

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

The original contents of fields are not stored in the Sphinx index.

yes

in-memory journaling

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

Role-based access control

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.