DBMS > CouchDB vs. EDB Postgres vs. Geode vs. RocksDB

System Properties Comparison CouchDB vs. EDB Postgres vs. Geode vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

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

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

Primary database model

Document store

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
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.90
Rank	#135	Overall
	#63	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

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

Website

Technical documentation

docs.couchdb.org/en/stable

www.enterprisedb.com/docs

geode.apache.org/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

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

EnterpriseDB

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

Facebook, Inc.

Initial release

2005

2002

2013

Current release

3.3.3, December 2023

14, December 2021

1.1, February 2017

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

BSD for PostgreSQL-components

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Erlang

Java

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

schema-free

yes

schema-free

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

standard with numerous extensions

SQL-like query language (OQL)

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java Client API
Memcached protocol
RESTful HTTP API

C++ API
Java API

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++
Delphi
Java
Perl
PHP
Python
Tcl

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning

by hash, list or range

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

yes, on a single node

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

Access rights per client and object definable

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.