DBMS > Atos Standard Common Repository vs. Percona Server for MongoDB vs. PlanetScale vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. Percona Server for MongoDB vs. PlanetScale vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.59
Rank	#151	Overall
	#70	Relational DBMS

Website

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

www.percona.com/mongodb/software/percona-server-for-mongodb

planetscale.com

yaacomo.com

Technical documentation

docs.percona.com/percona-distribution-for-mongodb

planetscale.com/docs

Developer

Atos Convergence Creators

Percona

PlanetScale

Q2WEB GmbH

Initial release

2016

2015

2020

2009

Current release

1703

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

Linux

Docker
Linux
macOS

Android
Linux
Windows

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

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

proprietary protocol using JSON

ADO.NET
JDBC
MySQL protocol
ODBC

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

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

JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

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

Atomic execution of specific operations

ACID at shard level

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

via In-Memory Engine

yes

User concepts

Access control

LDAP bind authentication

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights 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.

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

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

6 keys to MongoDB database security
22 May 2019, InfoWorld

Percona's DBMS Popularity Survey
25 June 2019, iProgrammer

provided by Google News

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

PlanetScale Ranked Number 188 Fastest-Growing Company in North America on the 2023 Deloitte Technology Fast ...
8 November 2023, businesswire.com

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

PlanetScale Named to Fortune 2023 Best Small Workplaces
31 August 2023, businesswire.com

Top 70+ startups in Database as a Service (DBaaS)
5 April 2024, Tracxn

provided by Google News

Share this page