DBMS > Riak TS vs. SAP HANA vs. Sphinx vs. Splice Machine

System Properties Comparison Riak TS vs. SAP HANA vs. Sphinx vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

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.25
Rank	#308	Overall
	#26	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	0.54
Rank	#255	Overall
	#116	Relational DBMS

Website

www.sap.com/products/hana.html

sphinxsearch.com

splicemachine.com

Technical documentation

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

help.sap.com/hana

sphinxsearch.com/docs

splicemachine.com/how-it-works

Developer

Open Source, formerly Basho Technologies

SAP

Sphinx Technologies Inc.

Splice Machine

Initial release

2015

2010

2001

2014

Current release

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

3.5.1, February 2023

3.1, March 2021

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0, 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

Erlang

C++

Java

Server operating systems

Linux
OS X

Appliance or cloud-service

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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.

Secondary indexes

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes, limited

yes

SQL-like query language (SphinxQL)

yes

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

Proprietary protocol

JDBC
Native Spark Datasource
ODBC

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Erlang

SQLScript, R

yes

Java

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

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

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

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

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

Access rights for users, groups and roles 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.