DBMS > Atos Standard Common Repository vs. Rockset vs. Vitess vs. XTDB

System Properties Comparison Atos Standard Common Repository vs. Rockset vs. Vitess vs. XTDB

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 scalable, reliable search and analytics service in the cloud, built on RocksDB

Scalable, distributed, cloud-native DBMS, extending MySQL

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Document store

Secondary database models

Relational DBMS
Search engine

Document store
Spatial DBMS

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

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

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

rockset.com

vitess.io

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.rockset.com

vitess.io/docs

www.xtdb.com/docs

Developer

Atos Convergence Creators

Rockset

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2016

2019

2013

2019

Current release

1703

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0, commercial licenses available

Open Source

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

Clojure

Server operating systems

Linux

hosted

Docker
Linux
macOS

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

dynamic typing

yes

yes, extensible-data-notation format

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

Read-only SQL queries, including JOINs

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

LDAP

HTTP REST

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

All languages with LDAP bindings

Go
Java
JavaScript (Node.js)
Python

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

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes, each node contains all data

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

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

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Access rights for users and organizations can be defined via Rockset console

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

OpenAI’s first acquisition is an enterprise data startup
21 June 2024, The Verge

OpenAI Looks To Boost Data Retrieval Capabilities Of Its GenAI Technology With Rockset Acquisition
26 June 2024, CRN

OpenAI acquires Rockset to enhance ChatGPT real-time data processing
25 June 2024, InfoWorld

An Analysis Of OpenAI’s Acquisition Of Rockset And Its Strategic Significance
24 June 2024, Forbes

OpenAI Buys Enterprise Startup to Help Customers Sift Through Data
21 June 2024, Bloomberg

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page