DBMS > Fauna vs. FoundationDB vs. GeoMesa vs. SQLite

System Properties Comparison Fauna vs. FoundationDB vs. GeoMesa vs. SQLite

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

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Spatial DBMS

Relational DBMS

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

Score	1.52
Rank	#153	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

fauna.com

github.com/apple/foundationdb

www.geomesa.org

www.sqlite.org

Technical documentation

docs.fauna.com

apple.github.io/foundationdb

www.geomesa.org/documentation/stable/user/index.html

www.sqlite.org/docs.html

Developer

Fauna, Inc.

FoundationDB

CCRi and others

Dwayne Richard Hipp

Initial release

2014

2013

2014

2000

Current release

6.2.28, November 2020

4.0.5, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.0

Open Source

Public Domain

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

Scala

C++

Scala

Server operating systems

hosted

Linux
OS X
Windows

server-less

Data scheme

schema-free

some layers support schemas

yes

dynamic column types

Typing

predefined data types such as float or date

some layers support typing

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

supported in specific SQL layer only

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

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

Server-side scripts

Stored procedures

user defined functions

in SQL-layer only

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

consistent hashing

Sharding

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

depending on storage layer

none

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

depending on storage layer

Foreign keys

Referential integrity

yes

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

via file-system locks

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.

depending on storage layer

yes

User concepts

Access control

Identity management, authentication, and access control

yes

depending on the DBMS used for storage

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.