DBMS > CouchDB vs. Google Cloud Firestore vs. Oracle NoSQL vs. Snowflake vs. TerarkDB

System Properties Comparison CouchDB vs. Google Cloud Firestore vs. Oracle NoSQL vs. Snowflake vs. TerarkDB

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 Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Document store
Key-value store
Relational DBMS

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

couchdb.apache.org

firebase.google.com/products/firestore

www.oracle.com/database/nosql/technologies/nosql

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

docs.couchdb.org/en/stable

firebase.google.com/docs/firestore

docs.oracle.com/en/database/other-databases/nosql-database/index.html

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

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

Google

Oracle

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2005

2017

2011

2014

2016

Current release

3.3.3, December 2023

23.3, December 2023

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

restricted open source version 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++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Linux
Solaris SPARC/x86

hosted

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

schema-free

Typing

predefined data types such as float or date

yes

optional

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

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP/JSON API

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

CLI Client
JDBC
ODBC

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Access rights for users and roles

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.