DBMS > Fauna vs. Geode vs. Memcached vs. Snowflake

System Properties Comparison Fauna vs. Geode vs. Memcached vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

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

In-memory key-value store, originally intended for caching

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

Primary database model

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Key-value store

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.92
Rank	#131	Overall
	#23	Key-value stores

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.fauna.com

geode.apache.org/docs

github.com/memcached/memcached/wiki

docs.snowflake.net/manuals/index.html

Developer

Fauna, Inc.

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

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Snowflake Computing Inc.

Initial release

2014

2002

2003

2014

Current release

1.1, February 2017

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD license

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

Scala

Java

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

yes

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

Typing

predefined data types such as float or date

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

SQL-like query language (OQL)

yes

APIs and other access methods

RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

consistent hashing

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

User concepts

Access control

Identity management, authentication, and access control

Access rights per client and object definable

yes

using SASL (Simple Authentication and Security Layer) protocol

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.