DBMS > Amazon Redshift vs. FoundationDB vs. IRONdb vs. Titan

System Properties Comparison Amazon Redshift vs. FoundationDB vs. IRONdb vs. Titan

Please select another system to include it in the comparison.

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.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines 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.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Titan is a Graph DBMS optimized for distributed clusters.

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Time Series DBMS

Graph DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.97
Rank	#191	Overall
	#32	Document stores
	#28	Key-value stores
	#87	Relational DBMS

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

www.circonus.com/solutions/time-series-database/

github.com/thinkaurelius/titan

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

docs.circonus.com/irondb/category/getting-started

github.com/thinkaurelius/titan/wiki

Developer

Amazon (based on PostgreSQL)

FoundationDB

Circonus LLC.

Aurelius, owned by DataStax

Initial release

2012

2013

2017

2012

Current release

6.2.28, November 2020

V0.10.20, January 2018

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache license, version 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

C++

C and C++

Java

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

Typing

predefined data types such as float or date

yes

some layers support typing

yes

text, numeric, histograms

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 query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JDBC
ODBC

HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Clojure
Java
Python

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

yes

via pluggable storage backends

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

yes

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

Immediate consistency per node, eventual consistency across nodes

Eventual 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

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

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.