DBMS > Riak KV vs. SAP SQL Anywhere vs. STSdb vs. ToroDB

System Properties Comparison Riak KV vs. SAP SQL Anywhere vs. STSdb vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed, fault tolerant key-value store

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Key-value store

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

Relational DBMS

Key-value store

Document store

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

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

Score	4.57
Rank	#78	Overall
	#43	Relational DBMS

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

www.sap.com/products/technology-platform/sql-anywhere.html

github.com/STSSoft/STSdb4

github.com/torodb/server

Technical documentation

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

OpenSource, formerly Basho Technologies

SAP

formerly Sybase

STS Soft SC

8Kdata

Initial release

2009

1992

2011

2016

Current release

3.2.0, December 2022

17, July 2015

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

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

Erlang

Java

Server operating systems

Linux
OS X

AIX
HP-UX
Linux
OS X
Solaris
Windows

Windows

All OS with a Java 7 VM

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

yes

string, integer, double, boolean, date, object_id

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

ADO.NET
HTTP API
JDBC
ODBC

.NET Client API

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
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

Erlang

yes, in C/C++, Java, .Net or Perl

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"

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

Database mirroring

none

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

User concepts

Access control

yes, using Riak Security

fine grained access rights according to SQL-standard

Access rights for users and roles

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

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Photos: Woodstock music graduate Alex Riak returns to work with students
11 December 2023, Shaw Local News Network

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

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

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

provided by Google News

SAP vulnerabilities Let Attacker Inject OS Commands—Patch Now!
11 July 2023, CybersecurityNews

SAP Again Named a Leader in 2021 Gartner® Magic Quadrant™ for Cloud Database Management Systems
16 December 2021, SAP News

SAP Products & Services Data Portfolio
2 July 2021, Datamation

AWS, IBM, Microsoft, Google emerge Cloud DBMS leaders
22 December 2022, Daily Host News

provided by Google News

Share this page