DBMS > Atos Standard Common Repository vs. Realm vs. Vitess vs. WakandaDB

System Properties Comparison Atos Standard Common Repository vs. Realm vs. Vitess vs. WakandaDB

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 DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Scalable, distributed, cloud-native DBMS, extending MySQL

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

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

realm.io

vitess.io

wakanda.github.io

Technical documentation

realm.io/docs

vitess.io/docs

wakanda.github.io/doc

Developer

Atos Convergence Creators

Realm, acquired by MongoDB in May 2019

The Linux Foundation, PlanetScale

Wakanda SAS

Initial release

2016

2014

2013

2012

Current release

1703

15.0.2, December 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

AGPLv3, extended commercial license 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++, JavaScript

Server operating systems

Linux

Android
Backend: server-less
iOS
Windows

Docker
Linux
macOS

Linux
OS X
Windows

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

LDAP

ADO.NET
JDBC
MySQL protocol
ODBC

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

.Net
Java

with Android only
Objective-C
React Native
Swift

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

JavaScript

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

yes

proprietary syntax

yes

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

none

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

Immediate Consistency

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

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

In-Memory realm

yes

User concepts

Access control

LDAP bind authentication

yes

Users with fine-grained authorization concept

no user groups or roles

yes

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

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

MongoDB aims to unify developer experience with launch of MongoDB Cloud
9 June 2020, diginomica

Danish CEO explains Silicon Valley learning curve for European entrepreneurs - San Francisco Business Times
6 October 2016, The Business Journals

Is Swift the Future of Server-side Development?
12 September 2017, Solutions Review

Kotlin Programming Language Will Surpass Java On Android Next Year
15 October 2017, Fossbytes

Java Synthetic Methods — What are these? | by Vaibhav Singh
27 February 2021, DataDrivenInvestor

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