DBMS > Heroic vs. Riak KV vs. Sadas Engine vs. SAP Advantage Database Server

System Properties Comparison Heroic vs. Riak KV vs. Sadas Engine vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Distributed, fault tolerant key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Time Series DBMS

Key-value store

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

Relational DBMS

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

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Website

github.com/spotify/heroic

www.sadasengine.com

www.sap.com/products/advantage-database-server.html

Technical documentation

spotify.github.io/heroic

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

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Spotify

OpenSource, formerly Basho Technologies

SADAS s.r.l.

Sybase, SAP

Initial release

2014

2009

2006

1993

Current release

3.2.0, December 2022

8.0

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version available

commercial

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

AIX
Linux
Windows

Linux
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

yes

via Elasticsearch

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

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

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Delphi
Perl
PHP

Server-side scripts

Stored procedures

Erlang

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"

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

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

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

managed by 'Learn by Usage'

caching of (temporary) tables can be configured

User concepts

Access control

yes, using Riak Security

Access rights for users, groups and roles according to SQL-standard

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.

Related products and services

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

More resources

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho Revamps Riak Open-Source Database
17 September 2014, InformationWeek

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

L'azienda italiana Advanced System colpita dal ransomware. Lo avverte l'azienda con un comunicato stampa
29 December 2022, Red Hot Cyber

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

Share this page