DBMS > EsgynDB vs. FoundationDB vs. Geode vs. Realm vs. Snowflake

System Properties Comparison EsgynDB vs. FoundationDB vs. Geode vs. Realm vs. Snowflake

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Primary database model

Relational DBMS

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	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.esgyn.cn

github.com/apple/foundationdb

geode.apache.org

realm.io

www.snowflake.com

Technical documentation

apple.github.io/foundationdb

geode.apache.org/docs

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Esgyn

FoundationDB

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

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Initial release

2015

2013

2002

2014

Current release

6.2.28, November 2020

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

commercial

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

C++

Java

Server operating systems

Linux

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Android
Backend: server-less
iOS
Windows

hosted

Data scheme

yes

schema-free

some layers support schemas

schema-free

yes

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

Typing

predefined data types such as float or date

yes

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

yes

supported in specific SQL layer only

SQL-like query language (OQL)

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

in SQL-layer only

user defined functions

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Cache Event Listeners

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

yes

Multi-source replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

yes

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

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.