DBMS > Galaxybase vs. MySQL vs. SAP HANA vs. Sequoiadb

System Properties Comparison Galaxybase vs. MySQL vs. SAP HANA vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable, ACID-compliant native distributed parallel graph platform

Widely used open source RDBMS

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

NewSQL database with distributed OLTP and SQL

Primary database model

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

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.00
Rank	#385	Overall
	#40	Graph DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.42
Rank	#263	Overall
	#41	Document stores
	#121	Relational DBMS

Website

galaxybase.com

www.mysql.com

www.sap.com/products/hana.html

www.sequoiadb.com

Technical documentation

dev.mysql.com/doc

help.sap.com/hana

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

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

Oracle

since 2010, originally MySQL AB, then Sun

SAP

Sequoiadb Ltd.

Initial release

2017

1995

2010

2013

Current release

Nov 20, November 2021

9.0.0, July 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

Server: AGPL; Client: Apache V2

Cloud-based only

Only available as a cloud service

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 and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

Linux

Data scheme

Strong typed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

proprietary protocol using JSON

Supported programming languages

Go
Java
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined procedures and functions

yes

proprietary syntax

SQLScript, R

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

yes

simple password-based access control

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.