DBMS > AgensGraph vs. Amazon Redshift vs. Atos Standard Common Repository vs. EsgynDB vs. OrigoDB

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Atos Standard Common Repository vs. EsgynDB vs. OrigoDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service for use with business intelligence tools

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

A fully ACID in-memory object graph database

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Document store
Key-value store

Relational DBMS

Document store
Object oriented DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

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

www.esgyn.cn

origodb.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

origodb.com/docs

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Atos Convergence Creators

Esgyn

Robert Friberg et al

Initial release

2016

2012

2016

2015

2009

under the name LiveDB

Current release

2.1, December 2018

1703

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

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

Server operating systems

Linux
OS X
Windows

hosted

Linux

Linux
Windows

Data scheme

depending on used data model

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

LDAP

ADO.NET
JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

All languages with LDAP bindings

All languages supporting JDBC/ODBC/ADO.Net

.Net

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Java Stored Procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

cell division

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication between multi datacenters

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

depending on model

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

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.