DBMS > Atos Standard Common Repository vs. Dgraph vs. Sequoiadb vs. Vitess

System Properties Comparison Atos Standard Common Repository vs. Dgraph vs. Sequoiadb vs. Vitess

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

Distributed and scalable native Graph DBMS

NewSQL database with distributed OLTP and SQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Graph DBMS

Document store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	0.42
Rank	#263	Overall
	#41	Document stores
	#121	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

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

dgraph.io

www.sequoiadb.com

vitess.io

Technical documentation

dgraph.io/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

vitess.io/docs

Developer

Atos Convergence Creators

Dgraph Labs, Inc.

Sequoiadb Ltd.

The Linux Foundation, PlanetScale

Initial release

2016

2013

Current release

1703

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache Version 2.0, commercial licenses 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++

Server operating systems

Linux

Linux
OS X
Windows

Linux

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

oid, date, timestamp, binary, regex

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

proprietary protocol using JSON

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

All languages with LDAP bindings

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

.Net
C++
Java
PHP
Python

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

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Source-replica replication

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

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

Document is locked during a transaction

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

User concepts

Access control

LDAP bind authentication

Planned for future releases

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

Top Open Source Graph Databases
3 June 2024, MarkTechPost

Dgraph on AWS: Setting up a horizontally scalable graph database
1 September 2020, AWS Blog

Graph Database Market size to grow by USD 7.40 billion between 2022 - 2027 | Growth Driven by Lack of standardization and programming flexibility - Technavio
13 December 2023, Yahoo Finance

Dgraph raises $11.5 million for scalable graph database solutions
31 July 2019, VentureBeat

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