DBMS > Amazon Redshift vs. OpenEdge vs. Riak TS vs. TerminusDB

System Properties Comparison Amazon Redshift vs. OpenEdge vs. Riak TS vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Application development environment with integrated database management system

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	3.69
Rank	#78	Overall
	#42	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

www.progress.com/openedge

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

documentation.progress.com/output/ua/OpenEdge_latest

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

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Progress Software Corporation

Open Source, formerly Basho Technologies

DataChemist Ltd.

Initial release

2012

1984

2015

2018

Current release

OpenEdge 12.2, March 2020

3.0.0, September 2022

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

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

restricted

yes

restricted

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

close to SQL 92

yes, limited

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

HTTP API
Native Erlang Interface

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

Progress proprietary ABL (Advanced Business Language)

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
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

Journaling Streams

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

informational only, not enforced by the system

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 journaling

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users and groups

Role-based access control

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.