DBMS > Atos Standard Common Repository vs. EsgynDB vs. Ingres vs. OrigoDB vs. TerarkDB

System Properties Comparison Atos Standard Common Repository vs. EsgynDB vs. Ingres vs. OrigoDB vs. TerarkDB

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Well established RDBMS

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

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	4.11
Rank	#81	Overall
	#44	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

www.esgyn.cn

www.actian.com/databases/ingres

origodb.com

github.com/bytedance/terarkdb

Technical documentation

docs.actian.com/ingres

origodb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Atos Convergence Creators

Esgyn

Actian Corporation

Robert Friberg et al

ByteDance, originally Terark

Initial release

2016

2015

1974

originally developed at University Berkely in early 1970s

2009

under the name LiveDB

2016

Current release

1703

11.2, May 2022

License

Commercial or Open Source

commercial

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

C++

Server operating systems

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
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

but tools for importing/exporting data from/to XML-files available

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

ADO.NET
JDBC
ODBC

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

All languages supporting JDBC/ODBC/ADO.Net

.Net

C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

Ingres Replicator

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

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

MVCC

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

fine grained access rights according to SQL-standard

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

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

PostgreSQL now top developer choice ahead of MySQL, according to massive new survey • DEVCLASS
13 June 2023, DevClass

Dr. Michael Stonebraker: A Short History of Database Systems
1 February 2019, The New Stack

provided by Google News

Share this page