DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. GeoSpock vs. SpaceTime

System Properties Comparison Amazon Redshift vs. Atos Standard Common Repository vs. GeoSpock vs. SpaceTime

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.

GeoSpock seems to be discontinued. Therefore it will be 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

Spatial and temporal data processing engine for extreme data scale

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	0.00
Rank	#396	Overall
	#8	Spatial DBMS

Website

aws.amazon.com/redshift

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

geospock.com

www.mireo.com/spacetime

Technical documentation

docs.aws.amazon.com/redshift

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

GeoSpock

Mireo

Initial release

2012

2016

2020

Current release

1703

2.0, September 2019

License

Commercial or Open Source

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

Java, Javascript

C++

Server operating systems

hosted

Linux

hosted

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

temporal, categorical

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

APIs and other access methods

JDBC
ODBC

LDAP

JDBC

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

C#
C++
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Real-time block device replication (DRBD)

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

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

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 can be defined per table

yes

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.