DBMS > Atos Standard Common Repository vs. Cassandra vs. PostGIS vs. Riak TS

System Properties Comparison Atos Standard Common Repository vs. Cassandra vs. PostGIS 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.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

Spatial extension of PostgreSQL

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

Wide column store

Spatial DBMS

Time Series DBMS

Secondary database models

Vector DBMS

starting with release V5

Relational DBMS

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

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

cassandra.apache.org

postgis.net

Technical documentation

cassandra.apache.org/doc/latest

postgis.net/documentation

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

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top level project, originally developped by Facebook

Open Source, formerly Basho Technologies

Initial release

2016

2008

2005

2015

Current release

1703

4.1.3, July 2023

3.4.2, February 2024

3.0.0, September 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

GPL v2.0

Open Source

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

Erlang

Server operating systems

Linux

BSD
Linux
OS X
Windows

Linux
OS X

Data scheme

Schema and schema-less with LDAP views

schema-free

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

restricted

only equality queries, not always the best performing solution

yes

restricted

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

yes

yes, limited

APIs and other access methods

LDAP

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

HTTP API
Native Erlang Interface

Supported programming languages

All languages with LDAP bindings

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

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

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

no "single point of failure"

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Representation of geographical distribution of servers is possible

yes

based on PostgreSQL

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

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

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

Atomicity and isolation are supported for single 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 object

yes

based on PostgreSQL

More information provided by the system vendor

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» 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.