DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. Dolt vs. Kinetica

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. Dolt vs. Kinetica

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

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

Fully vectorized database across both GPUs and CPUs

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Secondary database models

Document store

Spatial DBMS
Time Series DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Website

aws.amazon.com/redshift

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

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

www.kinetica.com

Technical documentation

docs.aws.amazon.com/redshift

docs.dolthub.com

docs.kinetica.com

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

DoltHub Inc

Kinetica

Initial release

2012

2016

2018

2012

Current release

1703

7.1, August 2021

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

C, C++

Server operating systems

hosted

Linux

Linux
macOS
Windows

Linux

Data scheme

yes

Schema and schema-less with LDAP views

yes

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

yes

SQL-like DML and DDL statements

APIs and other access methods

JDBC
ODBC

LDAP

CLI Client
HTTP REST

JDBC
ODBC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

currently in alpha release

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

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

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

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

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

GPU vRAM or System RAM

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

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

Access rights for users and roles on table level

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.