DBMS > PostGIS vs. RethinkDB vs. Riak KV

System Properties Comparison PostGIS vs. RethinkDB vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Distributed, fault tolerant key-value store

Primary database model

Spatial DBMS

Document store

Key-value store

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

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

postgis.net

rethinkdb.com

Technical documentation

postgis.net/documentation

rethinkdb.com/docs

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

Developer

The Linux Foundation

since July 2017

OpenSource, formerly Basho Technologies

Initial release

2005

2009

Current release

3.4.2, February 2024

2.4.1, August 2020

3.2.0, December 2022

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

Apache Version 2

Open Source

Apache version 2, commercial enterprise edition

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

C++

Erlang

Server operating systems

Linux
OS X
Windows

Linux
OS X

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

Supported programming languages

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

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

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

Client-side triggers through changefeeds

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

range based

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

Source-replica replication

selectable replication factor

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

Transaction concepts

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

ACID

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

users and table-level permissions

yes, using Riak Security

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

Meet some database management systems you are likely to hear more about in the future
4 August 2014, Paul Andlinger

show all

Recent citations in the news

An introduction to building realtime apps with RethinkDB
9 July 2022, devmio

How to Use RethinkDB with Node.js Applications — SitePoint
16 December 2015, SitePoint

Stripe acquires team behind NoSQL database startup RethinkDB
5 October 2016, VentureBeat

RethinkDB is dead, and MongoDB isn't what killed it
24 January 2017, TechRepublic

Open Source Horizon Claims Edge over Google's Firebase Mobile Back-End -- ADTmag
23 May 2016, ADT Magazine

provided by Google News

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

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

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

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

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page