DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. Dgraph vs. etcd vs. Oracle Coherence

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. Dgraph vs. etcd vs. Oracle Coherence

Editorial information provided by DB-Engines

Name

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

Description

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

Distributed and scalable native Graph DBMS

A distributed reliable key-value store

Oracles in-memory data grid solution

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS

Key-value store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

aws.amazon.com/redshift

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

dgraph.io

etcd.io
github.com/etcd-io/etcd

www.oracle.com/java/coherence

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.oracle.com/en/middleware/standalone/coherence

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Dgraph Labs, Inc.

Oracle

Initial release

2012

2016

2007

Current release

1703

3.4, August 2019

14.1, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

commercial

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

Server operating systems

hosted

Linux

Linux
OS X
Windows

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

LDAP

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

gRPC
JSON over HTTP

JCache
JPA
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.Net
C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

yes, watching key changes

yes

Live Events

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

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

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

Planned for future releases

authentification to access the cache via certificates or http basic authentication

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.