DBMS > Atos Standard Common Repository vs. Dolt vs. OrigoDB vs. TerarkDB

System Properties Comparison Atos Standard Common Repository vs. Dolt vs. OrigoDB vs. TerarkDB

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 MySQL compatible DBMS with Git-like versioning of data and schema

A fully ACID in-memory object graph database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Object oriented DBMS

Key-value store

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

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

github.com/dolthub/dolt
www.dolthub.com

origodb.com

github.com/bytedance/terarkdb

Technical documentation

docs.dolthub.com

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Atos Convergence Creators

DoltHub Inc

Robert Friberg et al

ByteDance, originally Terark

Initial release

2016

2018

2009

under the name LiveDB

2016

Current release

1703

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

commercial

restricted open source version 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
macOS
Windows

Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

CLI Client
HTTP REST

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

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

.Net

C++
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

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

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Only one user is configurable, and must be specified in the config file at startup

Role based authorization

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

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

provided by Google News

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Radar Trends to Watch: July 2022 – O'Reilly
5 July 2022, oreilly.com

Are you still not using Version Control for Data?
11 April 2020, Towards Data Science

provided by Google News

Share this page