DBMS > 4D vs. Atos Standard Common Repository vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Sequoiadb

System Properties Comparison 4D vs. Atos Standard Common Repository vs. BoltDB vs. Microsoft Azure Cosmos DB vs. Sequoiadb

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

An embedded key-value store for Go.

Globally distributed, horizontally scalable, multi-model database service

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

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

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

www.4d.com

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

github.com/boltdb/bolt

azure.microsoft.com/services/cosmos-db

www.sequoiadb.com

Technical documentation

developer.4d.com

learn.microsoft.com/azure/cosmos-db

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

4D, Inc

Atos Convergence Creators

Microsoft

Sequoiadb Ltd.

Initial release

1984

2016

2013

2014

2013

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

OS X
Windows

Linux

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

JSON types

yes

oid, date, timestamp, binary, regex

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

All properties auto-indexed by default

yes

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

LDAP

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

proprietary protocol using JSON

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

none

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

none

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual 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

yes

Multi-item ACID transactions with snapshot isolation within a partition

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

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 can be defined down to the item level

simple password-based access control

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.