DBMS > Amazon Redshift vs. HEAVY.AI vs. Oracle Berkeley DB vs. Postgres-XL

System Properties Comparison Amazon Redshift vs. HEAVY.AI vs. Oracle Berkeley DB vs. Postgres-XL

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Widely used in-process key-value store

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

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

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Website

aws.amazon.com/redshift

github.com/heavyai/heavydb
www.heavy.ai

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

www.postgres-xl.org

Technical documentation

docs.aws.amazon.com/redshift

docs.heavy.ai

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

www.postgres-xl.org/documentation

Developer

Amazon (based on PostgreSQL)

HEAVY.AI, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2016

1994

2014

since 2012, originally named StormDB

Current release

5.10, January 2022

18.1.40, May 2020

10 R1, October 2018

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; enterprise edition available

Open Source

commercial license available

Open Source

Mozilla public license

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++ and CUDA

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

Server operating systems

hosted

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
macOS

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

only with the Berkeley DB XML edition

yes

XML type, but no XML query functionality

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL interfaced based on SQLite is available

yes

distributed, parallel query execution

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/Thrift
Python

.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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

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

MVCC

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

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.