DBMS > Amazon Redshift vs. Blazegraph vs. Oracle Berkeley DB vs. Percona Server for MongoDB

System Properties Comparison Amazon Redshift vs. Blazegraph vs. Oracle Berkeley DB vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

Description

Large scale data warehouse service for use with business intelligence tools

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

Widely used in-process key-value store

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Relational DBMS

Graph DBMS
RDF store

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.81
Rank	#213	Overall
	#19	Graph DBMS
	#8	RDF stores

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

Score	0.60
Rank	#246	Overall
	#39	Document stores

Website

aws.amazon.com/redshift

blazegraph.com

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

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.aws.amazon.com/redshift

wiki.blazegraph.com

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

docs.percona.com/percona-distribution-for-mongodb

Developer

Amazon (based on PostgreSQL)

Blazegraph

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Percona

Initial release

2012

2006

1994

2015

Current release

2.1.5, March 2019

18.1.40, May 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

extended commercial license available

Open Source

commercial license available

Open Source

GPL Version 2

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)

C++

Server operating systems

hosted

Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

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

SPARQL is used as query language

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

proprietary protocol using JSON

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

.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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

yes

JavaScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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 depending on configuration

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in Graphs

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

via In-Memory Engine

User concepts

Access control

fine grained access rights according to SQL-standard

Security and Authentication via Web Application Container (Tomcat, Jetty)

Access rights for users and 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.