DBMS > 4D vs. CouchDB vs. Google Cloud Bigtable vs. Microsoft Azure Cosmos DB

System Properties Comparison 4D vs. CouchDB vs. Google Cloud Bigtable vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Document store

Key-value store
Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	2.68
Rank	#110	Overall
	#54	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Website

www.4d.com

couchdb.apache.org

cloud.google.com/bigtable

azure.microsoft.com/services/cosmos-db

Technical documentation

developer.4d.com

docs.couchdb.org/en/stable

cloud.google.com/bigtable/docs

learn.microsoft.com/azure/cosmos-db

Developer

4D, Inc

Apache Software Foundation

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

Google

Microsoft

Initial release

1984

2005

2015

2014

Current release

v20, April 2023

3.3.3, December 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Erlang

Server operating systems

OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

4D proprietary IDE
PHP

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

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

yes

View functions in JavaScript

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication
Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single document possible

Atomic single-row operations

Multi-item ACID transactions with snapshot isolation within a partition

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.

User concepts

Access control

Users and groups

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights can be defined down to the item level

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.