DBMS > Amazon Redshift vs. OpenEdge vs. Oracle NoSQL vs. OrigoDB

System Properties Comparison Amazon Redshift vs. OpenEdge vs. Oracle NoSQL vs. OrigoDB

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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Document store
Key-value store
Relational DBMS

Document store
Object oriented DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

aws.amazon.com/redshift

www.progress.com/openedge

www.oracle.com/database/nosql/technologies/nosql

origodb.com

Technical documentation

docs.aws.amazon.com/redshift

documentation.progress.com/output/ua/OpenEdge_latest

docs.oracle.com/en/database/other-databases/nosql-database/index.html

origodb.com/docs

Developer

Amazon (based on PostgreSQL)

Progress Software Corporation

Oracle

Robert Friberg et al

Initial release

2012

1984

2011

2009

under the name LiveDB

Current release

OpenEdge 12.2, March 2020

24.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Server operating systems

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
Solaris SPARC/x86

Linux
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

close to SQL 92

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

.NET Client API
HTTP API
LINQ

Supported programming languages

All languages supporting JDBC/ODBC

Progress proprietary ABL (Advanced Business Language)

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

depending on model

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users and groups

Access rights for users and roles

Role based authorization

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.