DBMS > CouchDB vs. FoundationDB vs. HugeGraph vs. SAP HANA

System Properties Comparison CouchDB vs. FoundationDB vs. HugeGraph vs. SAP HANA

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

A fast-speed and highly-scalable Graph DBMS

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Graph DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

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

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

couchdb.apache.org

github.com/apple/foundationdb

github.com/hugegraph
hugegraph.apache.org

www.sap.com/products/hana.html

Technical documentation

docs.couchdb.org/en/stable

apple.github.io/foundationdb

hugegraph.apache.org/docs

help.sap.com/hana

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

FoundationDB

Baidu

SAP

Initial release

2005

2013

2018

2010

Current release

3.3.3, December 2023

6.2.28, November 2020

0.9

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

C++

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
macOS
Unix

Appliance or cloud-service

Data scheme

schema-free

some layers support schemas

yes

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.

Secondary indexes

yes

via views

yes

also supports composite index and range index

yes

SQL

Support of SQL

supported in specific SQL layer only

yes

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP API
TinkerPop Gremlin

JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

Groovy
Java
Python

Server-side scripts

Stored procedures

View functions in JavaScript

in SQL-layer only

asynchronous Gremlin script jobs

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Linearizable consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

edges in graph

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

Access rights for users can be defined per database

Users, roles and permissions

yes

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.