DBMS > Amazon Redshift vs. Dgraph vs. OpenEdge vs. Oracle Berkeley DB vs. Oracle Rdb

System Properties Comparison Amazon Redshift vs. Dgraph vs. OpenEdge vs. Oracle Berkeley DB vs. Oracle Rdb

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

Application development environment with integrated database management system

Widely used in-process key-value store

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Website

aws.amazon.com/redshift

dgraph.io

www.progress.com/openedge

www.oracle.com/database/technologies/related/berkeleydb.html

www.oracle.com/database/technologies/related/rdb.html

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.oracle.com/cd/E17076_05/html/index.html

www.oracle.com/database/technologies/related/rdb-doc.html

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Progress Software Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Oracle, originally developed by Digital Equipment Corporation (DEC)

Initial release

2012

2016

1984

1994

1984

Current release

OpenEdge 12.2, March 2020

18.1.40, May 2020

7.4.1.1, 2021

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

commercial license available

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

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

hosted

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

HP Open VMS

Data scheme

yes

schema-free

yes

schema-free

Flexible Schema (defined schema, partial schema, 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

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

close to SQL 92

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

since Version 11.4

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes, on a single node

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

fine grained access rights according to SQL-standard

Planned for future releases

Users and groups

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.