DBMS > Amazon Redshift vs. FoundationDB vs. Spark SQL vs. Titan vs. WakandaDB

System Properties Comparison Amazon Redshift vs. FoundationDB vs. Spark SQL vs. Titan vs. WakandaDB

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.

Titan has been decommisioned after the takeover by Datastax. It will be removed from the DB-Engines ranking. A fork has been open-sourced as JanusGraph.

Description

Large scale data warehouse service for use with business intelligence tools

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Titan is a Graph DBMS optimized for distributed clusters.

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Graph DBMS

Object oriented DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

spark.apache.org/sql

github.com/thinkaurelius/titan

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

spark.apache.org/docs/latest/sql-programming-guide.html

github.com/thinkaurelius/titan/wiki

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

FoundationDB

Apache Software Foundation

Aurelius, owned by DataStax

Wakanda SAS

Initial release

2012

2013

2014

2012

Current release

6.2.28, November 2020

3.5.0 ( 2.13), September 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache license, version 2.0

Open Source

AGPLv3, extended commercial license available

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

Scala

Java

C++, JavaScript

Server operating systems

hosted

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

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

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

Java
Python
R
Scala

Clojure
Java
Python

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes, utilizing Spark Core

yes

via pluggable storage backends

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

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

yes

Relationships in graph

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

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

User authentification and security via Rexster Graph Server

yes

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.