DBMS > 4D vs. Atos Standard Common Repository vs. CouchDB vs. Databend vs. Google BigQuery

System Properties Comparison 4D vs. Atos Standard Common Repository vs. CouchDB vs. Databend vs. Google BigQuery

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Application development environment with integrated database management system

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

Large scale data warehouse service with append-only tables

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Website

www.4d.com

atos.net/en/convergence-creators/portfolio/standard-common-repository

couchdb.apache.org

github.com/datafuselabs/databend
www.databend.com

cloud.google.com/bigquery

Technical documentation

developer.4d.com

docs.couchdb.org/en/stable

docs.databend.com

cloud.google.com/bigquery/docs

Developer

4D, Inc

Atos Convergence Creators

Apache Software Foundation

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

Databend Labs

Google

Initial release

1984

2016

2005

2021

2010

Current release

v20, April 2023

1703

3.3.3, December 2023

1.0.59, April 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2.0

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

Java

Erlang

Rust

Server operating systems

OS X
Windows

Linux

Android
BSD
Linux
OS X
Solaris
Windows

hosted
Linux
macOS

hosted

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

yes

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

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

RESTful HTTP/JSON API

CLI Client
JDBC
RESTful HTTP API

RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

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

Go
Java
JavaScript (Node.js)
Python
Rust

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

improved architecture with release 2.0

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

atomic operations within a single document possible

yes

Since BigQuery is designed for querying data

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

Users and groups

LDAP bind authentication

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.