DBMS > Atos Standard Common Repository vs. GeoSpock vs. MaxDB vs. Riak TS

System Properties Comparison Atos Standard Common Repository vs. GeoSpock vs. MaxDB vs. Riak TS

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

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

A robust and reliable RDBMS optimized to run all major SAP solutions

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	2.15
Rank	#115	Overall
	#55	Relational DBMS

Score	0.17
Rank	#318	Overall
	#27	Time Series DBMS

Website

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

geospock.com

maxdb.sap.com

Technical documentation

maxdb.sap.com/documentation

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Atos Convergence Creators

GeoSpock

SAP, acquired from Software AG (Adabas-D) in 1997

Open Source, formerly Basho Technologies

Initial release

2016

1984

2015

Current release

1703

2.0, September 2019

7.9.10.12, February 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Limited community edition free

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

C++

Erlang

Server operating systems

Linux

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux
OS X

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

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

yes

temporal, categorical

yes

restricted

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

yes, limited

APIs and other access methods

LDAP

JDBC

ADO.NET
JDBC
ODBC
WebDAV

HTTP API
Native Erlang Interface

Supported programming languages

All languages with LDAP bindings

.Net
C#
Java
Perl
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

LDAP bind authentication

Access rights for users can be defined per table

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

nChain leads investment round in extreme-scale data firm GeoSpock
2 October 2020, CoinGeek

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

GeoSpock’s extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

CEO Richard Baker explores GeoSpock’s role in posting indexed data onto digital ledger
20 October 2020, CoinGeek

provided by Google News

SAP Content Server High Availability using Amazon EFS and SUSE
30 December 2020, AWS Blog

What is SAP S/4HANA?
21 March 2022, TechTarget

Hana triumphs, MaxDB lives on
24 September 2015, E3-Magazin

Google Cloud adds backup vaults and centralized management
10 September 2024, Blocks & Files

Researcher finds flaw in SAP's MaxDB
10 January 2008, ZDNet

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page