DBMS > H2GIS vs. Hyprcubd vs. MySQL vs. Teradata Aster vs. Trafodion

System Properties Comparison H2GIS vs. Hyprcubd vs. MySQL vs. Teradata Aster vs. Trafodion

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Teradata Aster has been integrated into other Teradata systems and therefore 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

Spatial extension of H2

Serverless Time Series DBMS

Widely used open source RDBMS

Platform for big data analytics on multistructured data sources and types

Transactional SQL-on-Hadoop DBMS

Primary database model

Spatial DBMS

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.h2gis.org

hyprcubd.com (offline)

www.mysql.com

trafodion.apache.org

Technical documentation

www.h2gis.org/docs/home

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

CNRS

Hyprcubd, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Teradata

Apache Software Foundation, originally developed by HP

Initial release

2013

1995

2005

2014

Current release

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

Open Source

LGPL 3.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

C++, Java

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

gRPC (https)

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
ODBC

Supported programming languages

Java

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

C
C#
C++
Java
Python
R

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

based on H2

yes

proprietary syntax

R packages

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

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

yes

based on H2

token access

Users with fine-grained authorization concept

no user groups or roles

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.