DBMS > Atos Standard Common Repository vs. GeoSpock vs. OceanBase vs. Snowflake

System Properties Comparison Atos Standard Common Repository vs. GeoSpock vs. OceanBase vs. Snowflake

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 distributed, high available RDBMS compatible with Oracle and MySQL

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Wide column store

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

Score	1.97
Rank	#119	Overall
	#58	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

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

geospock.com

en.oceanbase.com

www.snowflake.com

Technical documentation

en.oceanbase.com/docs/oceanbase-database

docs.snowflake.net/manuals/index.html

Developer

Atos Convergence Creators

GeoSpock

OceanBase

previously Alibaba and Ant Group

Snowflake Computing Inc.

Initial release

2016

2010

2014

Current release

1703

2.0, September 2019

4.3.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Commercial license available

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

Linux

hosted

Linux

hosted

Data scheme

Schema and schema-less with LDAP views

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

LDAP

JDBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

CLI Client
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

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

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.