DBMS > Altibase vs. Atos Standard Common Repository vs. Galaxybase vs. Snowflake vs. Trafodion

System Properties Comparison Altibase vs. Atos Standard Common Repository vs. Galaxybase vs. Snowflake vs. Trafodion

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

An enterprise grade, high-performance RDBMS

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

Scalable, ACID-compliant native distributed parallel graph platform

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Document store
Key-value store

Graph DBMS

Relational DBMS

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

Score	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

altibase.com

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

galaxybase.com

www.snowflake.com

trafodion.apache.org

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

docs.snowflake.net/manuals/index.html

trafodion.apache.org/documentation.html

Developer

Altibase

Atos Convergence Creators

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Snowflake Computing Inc.

Apache Software Foundation, originally developed by HP

Initial release

1999

2016

2017

2014

Current release

v7.3, 2023, August 2023

1703

Nov 20, November 2021

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

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

C++

Java

C and Java

C++, Java

Server operating systems

AIX
HP-UX
Linux

Linux

hosted

Linux

Data scheme

yes

Schema and schema-less with LDAP views

Strong typed schema

yes

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

yes

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

yes

SQL

Support of SQL

ANSI SQL-92

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

LDAP

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

C
C++
Java

All languages with LDAP bindings

Go
Java
Python

JavaScript (Node.js)
Python

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

stored procedures and stored functions

user defined procedures and functions

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

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

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

fine grained access rights according to SQL-standard

LDAP bind authentication

Role-based access control

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.