DBMS > 4D vs. Amazon DocumentDB vs. Atos Standard Common Repository vs. VoltDB

System Properties Comparison 4D vs. Amazon DocumentDB vs. Atos Standard Common Repository vs. VoltDB

Please select another system to include it in the comparison.

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

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store

Document store
Key-value store

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

www.4d.com

aws.amazon.com/documentdb

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

www.voltdb.com

Technical documentation

developer.4d.com

aws.amazon.com/documentdb/resources

docs.voltdb.com

Developer

4D, Inc

Atos Convergence Creators

VoltDB Inc.

Initial release

1984

2019

2016

2010

Current release

v20, April 2023

1703

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

OS X
Windows

hosted

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

Schema and schema-less with LDAP views

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

SQL

Support of SQL

yes

close to SQL 92

yes

only a subset of SQL 99

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

proprietary protocol using JSON (MongoDB compatible)

LDAP

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

Go
Java
JavaScript (Node.js)
PHP
Python

All languages with LDAP bindings

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

typically not used, however similar functionality with DBRef possible

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Atomic single-document operations

Atomic execution of specific operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Access rights for users and roles

LDAP bind authentication

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page