DBMS > FoundationDB vs. Greenplum vs. Ignite vs. RocksDB

System Properties Comparison FoundationDB vs. Greenplum vs. Ignite vs. RocksDB

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.

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Key-value store
Relational DBMS

Key-value store

Secondary database models

Document store
Spatial 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	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/apple/foundationdb

greenplum.org

ignite.apache.org

rocksdb.org

Technical documentation

apple.github.io/foundationdb

docs.greenplum.org

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

Developer

FoundationDB

Pivotal Software Inc.

Apache Software Foundation

Facebook, Inc.

Initial release

2013

2005

2015

2013

Current release

6.2.28, November 2020

7.0.0, September 2023

Apache Ignite 2.6

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

BSD

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

C++, Java, .Net

C++

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

some layers support schemas

yes

schema-free

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

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

Supported programming languages

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C
Java
Perl
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

yes

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Security Hooks for custom implementations

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.