DBMS > PostgreSQL vs. Riak KV vs. SurrealDB

System Properties Comparison PostgreSQL vs. Riak KV vs. SurrealDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Distributed, fault tolerant key-value store

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Key-value store

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

Document store
Graph DBMS

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Score	3.21
Rank	#82	Overall
	#11	Key-value stores

Score	1.08
Rank	#176	Overall
	#30	Document stores
	#16	Graph DBMS

Website

www.postgresql.org

surrealdb.com

Technical documentation

www.postgresql.org/docs

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

surrealdb.com/docs

Developer

PostgreSQL Global Development Group

www.postgresql.org/developer

OpenSource, formerly Basho Technologies

SurrealDB Ltd

Initial release

1989

1989: Postgres, 1996: PostgreSQL

2009

2022

Current release

16.4, August 2024

3.2.0, December 2022

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache version 2, commercial enterprise edition

Open Source

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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Erlang

Rust

Server operating systems

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Linux
OS X

Linux
macOS
Windows

Data scheme

yes

schema-free

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

partitioning by range, list and (since PostgreSQL 11) by hash

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

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

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

fine grained access rights according to SQL-standard

yes, using Riak Security

yes, based on authentication and database rules

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.