DBMS > Amazon Redshift vs. FoundationDB vs. Percona Server for MongoDB vs. RDF4J vs. SwayDB

System Properties Comparison Amazon Redshift vs. FoundationDB vs. Percona Server for MongoDB vs. RDF4J vs. SwayDB

Editorial information provided by DB-Engines

Name

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

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

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Document store

RDF store

Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.04
Rank	#387	Overall
	#61	Key-value stores

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

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

rdf4j.org

swaydb.simer.au

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

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

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

FoundationDB

Percona

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Simer Plaha

Initial release

2012

2013

2015

2004

2018

Current release

6.2.28, November 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL Version 2

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GNU Affero GPL V3.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

C++

Java

Scala

Server operating systems

hosted

Linux
OS X
Windows

Linux

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

some layers support schemas

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

supported in specific SQL layer only

APIs and other access methods

JDBC
ODBC

proprietary protocol using JSON

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

Java
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

in SQL-layer only

Transaction concepts

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

ACID

Isolation support depends on the API used

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.