DBMS > Amazon Redshift vs. Badger vs. Blueflood vs. Oracle Berkeley DB vs. SAP SQL Anywhere

System Properties Comparison Amazon Redshift vs. Badger vs. Blueflood vs. Oracle Berkeley DB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Scalable TimeSeries DBMS based on Cassandra

Widely used in-process key-value store

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

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

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Website

aws.amazon.com/redshift

github.com/dgraph-io/badger

blueflood.io

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

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.aws.amazon.com/redshift

godoc.org/github.com/dgraph-io/badger

github.com/rax-maas/blueflood/wiki

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

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Amazon (based on PostgreSQL)

DGraph Labs

Rackspace

Oracle

originally developed by Sleepycat, which was acquired by Oracle

SAP

formerly Sybase

Initial release

2012

2017

2013

1994

1992

Current release

18.1.40, May 2020

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

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

Java

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

Server operating systems

hosted

BSD
Linux
OS X
Solaris
Windows

Linux
OS X

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

predefined scheme

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

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

APIs and other access methods

JDBC
ODBC

HTTP REST

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.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

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in C/C++, Java, .Net or Perl

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

based on Cassandra

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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.