DBMS > Amazon Redshift vs. Hazelcast vs. OpenEdge vs. Oracle Berkeley DB vs. Vitess

System Properties Comparison Amazon Redshift vs. Hazelcast vs. OpenEdge vs. Oracle Berkeley DB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted in-memory data grid

Application development environment with integrated database management system

Widely used in-process key-value store

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

aws.amazon.com/redshift

hazelcast.com

www.progress.com/openedge

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

vitess.io

Technical documentation

docs.aws.amazon.com/redshift

hazelcast.org/imdg/docs

documentation.progress.com/output/ua/OpenEdge_latest

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

vitess.io/docs

Developer

Amazon (based on PostgreSQL)

Hazelcast

Progress Software Corporation

Oracle

originally developed by Sleepycat, which was acquired by Oracle

The Linux Foundation, PlanetScale

Initial release

2012

2008

1984

1994

2013

Current release

5.3.6, November 2023

OpenEdge 12.2, March 2020

18.1.40, May 2020

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

commercial license available

Open Source

Apache Version 2.0, commercial licenses available

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

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

Server operating systems

hosted

All OS with a Java VM

AIX
HP-UX
Linux
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

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

the object must implement a serialization strategy

yes

only with the Berkeley DB XML edition

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

close to SQL 92

yes

SQL interfaced based on SQLite is available

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

Events

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

since Version 11.4

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Source-replica replication

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Role-based access control

Users and groups

Users with fine-grained authorization concept

no user groups or roles

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.