DBMS > Galaxybase vs. Google BigQuery vs. SAP HANA vs. Trafodion

System Properties Comparison Galaxybase vs. Google BigQuery vs. SAP HANA vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

Scalable, ACID-compliant native distributed parallel graph platform

Large scale data warehouse service with append-only tables

In-memory, column based data store. Available as appliance or cloud service

Transactional SQL-on-Hadoop DBMS

Primary database model

Graph DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

galaxybase.com

cloud.google.com/bigquery

www.sap.com/products/hana.html

trafodion.apache.org

Technical documentation

cloud.google.com/bigquery/docs

help.sap.com/hana

trafodion.apache.org/documentation.html

Developer

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

Google

SAP

Apache Software Foundation, originally developed by HP

Initial release

2017

2010

2014

Current release

Nov 20, November 2021

2.0 SPS07 (April 4, 2023), April 2023

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and Java

C++, Java

Server operating systems

Linux

hosted

Appliance or cloud-service

Linux

Data scheme

Strong typed schema

yes

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

RESTful HTTP/JSON API

JDBC
ODBC

ADO.NET
JDBC
ODBC

Supported programming languages

Go
Java
Python

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined procedures and functions

user defined functions

in JavaScript

SQLScript, R

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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

Role-based access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

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.