DBMS > FoundationDB vs. Geode vs. PouchDB vs. SQLite vs. Trafodion

System Properties Comparison FoundationDB vs. Geode vs. PouchDB vs. SQLite vs. Trafodion

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store

Document store

Relational DBMS

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

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/apple/foundationdb

Technical documentation

apple.github.io/foundationdb

geode.apache.org/docs

pouchdb.com/guides

www.sqlite.org/docs.html

trafodion.apache.org/documentation.html

Developer

FoundationDB

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Dwayne Richard Hipp

Apache Software Foundation, originally developed by HP

Initial release

2013

2002

2012

2000

2014

Current release

6.2.28, November 2020

1.1, February 2017

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Public Domain

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java

JavaScript

C++, Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Linux

Data scheme

schema-free

some layers support schemas

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

some layers support typing

yes

not rigid because of 'dynamic typing' concept.

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

yes

via views

yes

SQL

Support of SQL

supported in specific SQL layer only

SQL-like query language (OQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
All JVM based languages
C++
Groovy
Java
Scala

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

in SQL-layer only

user defined functions

View functions in JavaScript

Java Stored Procedures

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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

Eventual 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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Access rights per client and object definable

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.