DBMS > Amazon Redshift vs. BigchainDB vs. Blazegraph vs. Derby vs. FoundationDB

System Properties Comparison Amazon Redshift vs. BigchainDB vs. Blazegraph vs. Derby vs. FoundationDB

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.

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Description

Large scale data warehouse service for use with business intelligence tools

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Ordered key-value store. Core features are complimented by layers.

Primary database model

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.85
Rank	#208	Overall
	#35	Document stores

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Website

aws.amazon.com/redshift

www.bigchaindb.com

blazegraph.com

db.apache.org/derby

github.com/apple/foundationdb

Technical documentation

docs.aws.amazon.com/redshift

bigchaindb.readthedocs.io/en/latest

wiki.blazegraph.com

db.apache.org/derby/manuals/index.html

apple.github.io/foundationdb

Developer

Amazon (based on PostgreSQL)

Blazegraph

Apache Software Foundation

FoundationDB

Initial release

2012

2016

2006

1997

2013

Current release

2.1.5, March 2019

10.17.1.0, November 2023

6.2.28, November 2020

License

Commercial or Open Source

commercial

Open Source

AGPL v3

Open Source

extended commercial license available

Open Source

Apache version 2

Open Source

Apache 2.0

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

Python

Java

C++

Server operating systems

hosted

Linux

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

some layers support schemas

Typing

predefined data types such as float or date

yes

RDF literal types

yes

some layers support typing

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SPARQL is used as query language

yes

supported in specific SQL layer only

APIs and other access methods

JDBC
ODBC

CLI Client
RESTful HTTP API

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

JDBC

Supported programming languages

All languages supporting JDBC/ODBC

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Java

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Java Stored Procedures

in SQL-layer only

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Linearizable consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Relationships in Graphs

yes

in SQL-layer only

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

yes,with MongoDB ord RethinkDB

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

yes

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

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.