DBMS > Atos Standard Common Repository vs. etcd vs. Machbase Neo vs. PlanetScale

System Properties Comparison Atos Standard Common Repository vs. etcd vs. Machbase Neo 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

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

A distributed reliable key-value store

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Document store
Key-value store

Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	7.05
Rank	#53	Overall
	#5	Key-value stores

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Website

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

etcd.io
github.com/etcd-io/etcd

machbase.com

planetscale.com

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

machbase.com/dbms

planetscale.com/docs

Developer

Atos Convergence Creators

Machbase

PlanetScale

Initial release

2016

2013

2020

Current release

1703

3.4, August 2019

V8.0, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

free test version 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.

Implementation language

Java

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

Linux
macOS
Windows

Docker
Linux
macOS

Data scheme

Schema and schema-less with LDAP views

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

LDAP

gRPC
JSON over HTTP

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

proprietary syntax

Triggers

yes

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

selectable replication factor

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 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

volatile and lookup table

yes

User concepts

Access control

LDAP bind authentication

simple password-based access control

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

ETCD guidelines: RBI seeks to balance rupee stability, competitiveness | Policy Circle
8 April 2024, Policy Circle

Public preview: AKS cluster control plane metrics in managed Prometheus
12 February 2024, Microsoft

Is Your etcd an Open Door for Cyber Attacks? How to Secure Your Kubernetes Clusters & Nodes
8 November 2023, Information Security Newspaper

Monitor Amazon EKS Control Plane metrics using AWS Open Source monitoring services
12 October 2023, AWS Blog

6 Cool Kubernetes Operators and How to Use Them
22 January 2024, hackernoon.com

provided by Google News

PlanetScale ends free tier bid, sheds staff in profitability bid
11 March 2024, The Register

PlanetScale Insights Anomalies introduces smart query monitoring
29 November 2023, SDTimes.com

PlanetScale forks MySQL to add vector support
3 October 2023, TechCrunch

Top Database as a Service (DBaaS) Startups
28 August 2024, Tracxn

PlanetScale review: Horizontally scalable MySQL in the cloud
1 September 2021, InfoWorld

provided by Google News

Share this page