DBMS > Atos Standard Common Repository vs. GridDB vs. Snowflake vs. Trafodion

System Properties Comparison Atos Standard Common Repository vs. GridDB vs. Snowflake vs. Trafodion

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.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Scalable in-memory time series database optimized for IoT and Big Data

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

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

griddb.net

www.snowflake.com

trafodion.apache.org

Technical documentation

docs.griddb.net

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Atos Convergence Creators

Toshiba Corporation

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

2016

2013

2014

Current release

1703

5.1, August 2022

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

Apache 2.0

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

C++

C++, Java

Server operating systems

Linux

hosted

Linux

Data scheme

Schema and schema-less with LDAP views

yes

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

yes

Typing

predefined data types such as float or date

optional

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

APIs and other access methods

LDAP

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate consistency within container, eventual consistency across containers

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 at container level

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 database

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

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.