DBMS > CouchDB vs. Firebase Realtime Database vs. GridGain vs. Oracle vs. Oracle Berkeley DB

System Properties Comparison CouchDB vs. Firebase Realtime Database vs. GridGain vs. Oracle vs. Oracle Berkeley DB

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.

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

GridGain is an in-memory computing platform, built on Apache Ignite

Widely used RDBMS

Widely used in-process key-value store

Primary database model

Document store

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Website

couchdb.apache.org

firebase.google.com/products/realtime-database

www.gridgain.com

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

docs.couchdb.org/en/stable

firebase.google.com/docs/database

www.gridgain.com/docs/index.html

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Apache Software Foundation

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

Google

acquired by Google 2014

GridGain Systems, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2005

2012

2007

1980

1994

Current release

3.3.3, December 2023

GridGain 8.5.1

23c, September 2023

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache version 2

commercial

commercial, open source

commercial

restricted free version is available

Open Source

commercial license available

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

Erlang

Java, C++, .Net, Python, REST, SQL

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

only with the Berkeley DB XML edition

Secondary indexes

yes

via views

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

RESTful HTTP/JSON API

Android
iOS
JavaScript API
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

Java
JavaScript
Objective-C

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

limited functionality with using 'rules'

yes (compute grid and cache interceptors can be used instead)

PL/SQL

also stored procedures in Java possible

Triggers

yes

Callbacks are triggered when data changes

yes (cache interceptors and events)

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes (replicated cache)

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate 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

yes

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Access rights for users can be defined per database

yes, based on authentication and database rules

Role-based access control
Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.