DBMS > Amazon Redshift vs. FoundationDB vs. Graph Engine vs. OpenTSDB vs. TerarkDB

System Properties Comparison Amazon Redshift vs. FoundationDB vs. Graph Engine vs. OpenTSDB vs. TerarkDB

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 distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Scalable Time Series DBMS based on HBase

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Graph DBMS
Key-value store

Time Series DBMS

Key-value store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	1.07
Rank	#188	Overall
	#31	Document stores
	#28	Key-value stores
	#86	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	1.73
Rank	#147	Overall
	#12	Time Series DBMS

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

aws.amazon.com/redshift

github.com/apple/foundationdb

www.graphengine.io

opentsdb.net

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

apple.github.io/foundationdb

www.graphengine.io/docs/manual

opentsdb.net/docs/build/html/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

FoundationDB

Microsoft

currently maintained by Yahoo and other contributors

ByteDance, originally Terark

Initial release

2012

2013

2010

2011

2016

Current release

6.2.28, November 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

MIT License

Open Source

LGPL

commercial

restricted open source version 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++

.NET and C

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

.NET

Linux
Windows

Data scheme

yes

schema-free

some layers support schemas

yes

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

yes

numeric data for metrics, strings for tags

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

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

RESTful HTTP API

HTTP API
Telnet API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
F#
Visual Basic

Erlang
Go
Java
Python
R
Ruby

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

in SQL-layer only

yes

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Immediate Consistency

based on HBase

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.