DBMS > PostGIS vs. Riak KV vs. STSdb vs. ToroDB vs. Yanza

System Properties Comparison PostGIS vs. Riak KV vs. STSdb vs. ToroDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

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

Description

Spatial extension of PostgreSQL

Distributed, fault tolerant key-value store

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

Time Series DBMS for IoT Applications

Primary database model

Spatial DBMS

Key-value store

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

Key-value store

Document store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

postgis.net

github.com/STSSoft/STSdb4

github.com/torodb/server

yanza.com

Technical documentation

postgis.net/documentation

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

Developer

OpenSource, formerly Basho Technologies

STS Soft SC

8Kdata

Yanza

Initial release

2005

2009

2011

2016

2015

Current release

3.4.2, February 2024

3.2.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

Windows

All OS with a Java 7 VM

Windows

Data scheme

yes

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

yes

restricted

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API

HTTP 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#
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

no "single point of failure"

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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.

User concepts

Access control

yes

based on PostgreSQL

yes, using Riak Security

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

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

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

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

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page