DBMS > Altibase vs. Atos Standard Common Repository vs. MySQL vs. PlanetScale

System Properties Comparison Altibase vs. Atos Standard Common Repository vs. MySQL vs. PlanetScale

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

An enterprise grade, high-performance RDBMS

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

Widely used open source RDBMS

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Website

altibase.com

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

www.mysql.com

planetscale.com

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

dev.mysql.com/doc

planetscale.com/docs

Developer

Altibase

Atos Convergence Creators

Oracle

since 2010, originally MySQL AB, then Sun

PlanetScale

Initial release

1999

2016

1995

2020

Current release

v7.3, 2023, August 2023

1703

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

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

Implementation language

C++

Java

C and C++

Server operating systems

AIX
HP-UX
Linux

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS

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

ANSI SQL-92

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol

LDAP

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C++
Java

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

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

proprietary syntax

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

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

yes

not for MyISAM storage engine

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 at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

fine grained access rights according to SQL-standard

LDAP bind authentication

Users with fine-grained authorization concept

no user groups or roles

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.