DBMS > FoundationDB vs. Snowflake vs. Tigris vs. Trafodion

System Properties Comparison FoundationDB vs. Snowflake vs. Tigris vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Cloud-based data warehousing service for structured and semi-structured data

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Relational DBMS

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

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

github.com/apple/foundationdb

www.snowflake.com

www.tigrisdata.com

trafodion.apache.org

Technical documentation

apple.github.io/foundationdb

docs.snowflake.net/manuals/index.html

www.tigrisdata.com/docs

trafodion.apache.org/documentation.html

Developer

FoundationDB

Snowflake Computing Inc.

Tigris Data, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2013

2014

2022

2014

Current release

6.2.28, November 2020

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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

C++

C++, Java

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS
Windows

Linux

Data scheme

schema-free

some layers support schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

CLI Client
JDBC
ODBC

CLI Client
gRPC
RESTful HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

JavaScript (Node.js)
Python

Go
Java
JavaScript (Node.js)

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

Java Stored Procedures

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

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, using FoundationDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

Access rights for users and roles

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.