DBMS > Amazon Redshift vs. Atos Standard Common Repository vs. GeoSpock vs. Heroic vs. LokiJS

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

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

In-memory JavaScript DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Time Series DBMS

Document store

Secondary database models

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.43
Rank	#264	Overall
	#42	Document stores

Website

aws.amazon.com/redshift

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

geospock.com

github.com/spotify/heroic

github.com/techfort/LokiJS

Technical documentation

docs.aws.amazon.com/redshift

spotify.github.io/heroic

techfort.github.io/LokiJS

Developer

Amazon (based on PostgreSQL)

Atos Convergence Creators

GeoSpock

Spotify

Initial release

2012

2016

2014

Current release

1703

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

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

Java

JavaScript

Server operating systems

hosted

Linux

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Data scheme

yes

Schema and schema-less with LDAP views

yes

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

temporal, categorical

yes

via Elasticsearch

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

APIs and other access methods

JDBC
ODBC

LDAP

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

JavaScript API

Supported programming languages

All languages supporting JDBC/ODBC

All languages with LDAP bindings

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

none

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

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

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.