DBMS > PostGIS vs. Riak KV vs. STSdb vs. VoltDB

System Properties Comparison PostGIS vs. Riak KV vs. STSdb vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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

Relational DBMS

Secondary database models

Relational DBMS

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

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

postgis.net

github.com/STSSoft/STSdb4

www.voltdb.com

Technical documentation

postgis.net/documentation

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

docs.voltdb.com

Developer

OpenSource, formerly Basho Technologies

STS Soft SC

VoltDB Inc.

Initial release

2005

2009

2011

2010

Current release

3.4.2, February 2024

3.2.0, December 2022

4.0.8, September 2015

11.3, April 2022

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 for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

Linux
OS X

Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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.

yes

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

HTTP API
Native Erlang Interface

.NET Client API

Java API
JDBC
RESTful HTTP/JSON 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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Erlang

Java

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

no "single point of failure"

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

none

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

links between data sets can be stored

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

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

If you wagered Bet365 would buy up Basho's remains, you'd be a big winner right now
25 August 2017, The Register

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

Unveiling Volt Active Data’s game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Announces Key New Hires
26 October 2021, citybiz

Solutions Review Sits Down with VoltDB CEO David Flower
17 April 2018, Solutions Review

VoltDB Aims for Fast Big Data Development
29 January 2015, ADT Magazine

provided by Google News

Share this page