DBMS > PostGIS vs. Riak TS vs. Snowflake vs. Teradata

System Properties Comparison PostGIS vs. Riak TS vs. Snowflake vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Spatial extension of PostgreSQL

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 hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

postgis.net

www.snowflake.com

www.teradata.com

Technical documentation

postgis.net/documentation

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

docs.snowflake.net/manuals/index.html

docs.teradata.com

Developer

Open Source, formerly Basho Technologies

Snowflake Computing Inc.

Teradata

Initial release

2005

2015

2014

1984

Current release

3.4.2, February 2024

3.0.0, September 2022

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

GPL v2.0

Open Source

commercial

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

Erlang

Server operating systems

Linux
OS X

hosted

hosted
Linux

Data scheme

yes

schema-free

yes

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

yes

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

Secondary indexes

yes

restricted

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

yes, limited

yes

SQL 2016 + extensions

APIs and other access methods

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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

JavaScript (Node.js)
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

Erlang

user defined functions

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

yes

based on PostgreSQL

Sharding

yes

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

selectable replication factor

yes

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

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.

yes

User concepts

Access control

yes

based on PostgreSQL

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

fine grained access rights according to SQL-standard

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.