DBMS > Atos Standard Common Repository vs. MaxDB vs. Postgres-XL vs. Vitess

System Properties Comparison Atos Standard Common Repository vs. MaxDB vs. Postgres-XL vs. Vitess

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

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

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

maxdb.sap.com

www.postgres-xl.org

vitess.io

Technical documentation

maxdb.sap.com/documentation

www.postgres-xl.org/documentation

vitess.io/docs

Developer

Atos Convergence Creators

SAP, acquired from Software AG (Adabas-D) in 1997

The Linux Foundation, PlanetScale

Initial release

2016

1984

2014

since 2012, originally named StormDB

2013

Current release

1703

7.9.10.12, February 2024

10 R1, October 2018

15.0.2, December 2022

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Mozilla public license

Open Source

Apache Version 2.0, commercial licenses available

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.

Implementation language

Java

C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS

Docker
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

with proprietary extensions

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC
WebDAV

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C#
Java
Perl
PHP
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

Server-side scripts

Stored procedures

yes

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID

MVCC

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

LDAP bind authentication

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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

Recent citations in the news

SAP Content Server High Availability using Amazon EFS and SUSE | Amazon Web Services
30 December 2020, AWS Blog

Extended Maintenance Commitments Across SAP Solutions
11 August 2020, SAP News

What is SAP S/4HANA?
21 March 2022, TechTarget

IBM Cloud SAP-Certified Infrastructure Features
22 January 2019, ibm.com

Alibaba Cloud Offers Access to SAP Software for Customers
5 June 2018, Alizila

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page