DBMS > Greenplum vs. Newts vs. Riak TS vs. Snowflake vs. SurrealDB

System Properties Comparison Greenplum vs. Newts vs. Riak TS vs. Snowflake vs. SurrealDB

Editorial information provided by DB-Engines

Name

Description

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Time Series DBMS based on Cassandra

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

Document store
Graph DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	8.08
Rank	#48	Overall
	#31	Relational DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

greenplum.org

opennms.github.io/newts

www.snowflake.com

surrealdb.com

Technical documentation

docs.greenplum.org

github.com/OpenNMS/newts/wiki

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

docs.snowflake.net/manuals/index.html

surrealdb.com/docs

Developer

Pivotal Software Inc.

OpenNMS Group

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

SurrealDB Ltd

Initial release

2005

2014

2015

2014

2022

Current release

7.0.0, September 2023

3.0.0, September 2022

v1.5.0, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

commercial

Open Source

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Erlang

Rust

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X

hosted

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

since Version 4.2

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

yes, limited

yes

SQL-like query language

APIs and other access methods

JDBC
ODBC

HTTP REST
Java API

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

C
Java
Perl
Python
R

Java

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

JavaScript (Node.js)
Python

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

yes

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

based on Cassandra

selectable replication factor

yes

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

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between datasets 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.

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.