DBMS > Heroic vs. Riak TS vs. Sphinx vs. YottaDB

System Properties Comparison Heroic vs. Riak TS vs. Sphinx vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

A fast and solid embedded Key-value store

Primary database model

Time Series DBMS

Search engine

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Score	0.21
Rank	#309	Overall
	#43	Key-value stores

Website

github.com/spotify/heroic

sphinxsearch.com

yottadb.com

Technical documentation

spotify.github.io/heroic

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

sphinxsearch.com/docs

yottadb.com/resources/documentation

Developer

Spotify

Open Source, formerly Basho Technologies

Sphinx Technologies Inc.

YottaDB, LLC

Initial release

2014

2015

2001

Current release

3.0.0, September 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2, commercial licence available

Open Source

AGPL 3.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

C++

Server operating systems

Linux
OS X

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Docker
Linux

Data scheme

schema-free

yes

schema-free

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

via Elasticsearch

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes, limited

SQL-like query language (SphinxQL)

by using the Octo plugin

APIs and other access methods

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API
Native Erlang Interface

Proprietary protocol

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

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
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

yes

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

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

optimistic locking

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 capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Users and groups based on OS-security mechanisms

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the news

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose?
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Beyond the Concert Hall: 5 Organizations Making a Difference in Classical Music in 2018
22 December 2018, WQXR Radio

Here’s Why Russia Is Cracking Down on Google
23 February 2015, TIME

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

provided by Google News

Share this page