DBMS > 4D vs. Atos Standard Common Repository vs. MySQL vs. OpenTenBase

System Properties Comparison 4D vs. Atos Standard Common Repository vs. MySQL vs. OpenTenBase

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

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

Widely used open source RDBMS

An enterprise-level distributed HTAP open source database based on PostgreSQL

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

www.4d.com

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

www.mysql.com

github.com/OpenTenBase/OpenTenBase
www.opentenbase.org

Technical documentation

developer.4d.com

dev.mysql.com/doc

docs.opentenbase.org
docs.opentenbase.org/en

Developer

4D, Inc

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

OpenAtom Foundation, previously Tencent

Initial release

1984

2016

1995

Current release

v20, April 2023

1703

8.3.0, January 2024

2.5, January 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-3

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

OS X
Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

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

with proprietary extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
Go
Java
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Access rights for users, groups and roles according to SQL-standard

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.