DBMS > Atos Standard Common Repository vs. JaguarDB vs. PlanetScale vs. Transbase

System Properties Comparison Atos Standard Common Repository vs. JaguarDB vs. PlanetScale vs. Transbase

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

Performant, highly scalable DBMS for AI and IoT applications

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.00
Rank	#385	Overall
	#61	Key-value stores
	#16	Vector DBMS

Score	1.09
Rank	#178	Overall
	#82	Relational DBMS

Score	0.05
Rank	#355	Overall
	#150	Relational DBMS

Website

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

www.jaguardb.com

planetscale.com

www.transaction.de/en/products/transbase.html

Technical documentation

www.jaguardb.com/support.html

planetscale.com/docs

www.transaction.de/en/products/transbase/features.html

Developer

Atos Convergence Creators

DataJaguar, Inc.

PlanetScale

Transaction Software GmbH

Initial release

2016

2015

2020

1987

Current release

1703

3.3 July 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

free development license

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

the server part. Clients available in other languages

C and C++

Server operating systems

Linux

Docker
Linux
macOS

FreeBSD
Linux
macOS
Solaris
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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

yes

APIs and other access methods

LDAP

JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

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

Multi-source replication

Multi-source replication
Source-replica 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

Eventual 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

yes

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

User concepts

Access control

LDAP bind authentication

rights management via user accounts

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

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