DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. etcd vs. Teradata Aster

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. etcd vs. Teradata Aster

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.

Teradata Aster has been integrated into other Teradata systems and therefore 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

A distributed reliable key-value store

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

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

Website

aws.amazon.com/redshift

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

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

Technical documentation

docs.aws.amazon.com/redshift

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

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

Teradata

Initial release

2012

2016

2005

Current release

1703

3.4, August 2019

License

Commercial or Open Source

commercial

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

FreeBSD
Linux
Windows

experimental

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

in Aster File Store

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

LDAP

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

R packages

Triggers

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Concurrency

Support for concurrent manipulation of data

yes

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

fine grained access rights according to SQL-standard

LDAP bind authentication

fine grained access rights according to SQL-standard

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.