DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. ToroDB vs. Vertica

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. ToroDB vs. Vertica

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.

ToroDB seems to be discontinued. Therefore it is excluded 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 MongoDB-compatible JSON document store, built on top of PostgreSQL

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

Document store
Key-value store

Document store

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

aws.amazon.com/redshift

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

github.com/torodb/server

www.vertica.com

Technical documentation

docs.aws.amazon.com/redshift

vertica.com/documentation

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

8Kdata

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2016

2005

Current release

1703

12.0.3, January 2023

License

Commercial or Open Source

commercial

Open Source

AGPL-V3

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

hosted

Linux

All OS with a Java 7 VM

Linux

Data scheme

yes

Schema and schema-less with LDAP views

schema-free

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

Typing

predefined data types such as float or date

yes

optional

yes

string, integer, double, boolean, date, object_id

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

does not fully support an SQL-standard

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

JDBC
ODBC

LDAP

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

user defined functions

in Python

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

Immediate Consistency

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

User concepts

Access control

fine grained access rights according to SQL-standard

LDAP bind authentication

Access rights for users and roles

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.