DBMS > GeoSpock vs. HBase vs. MySQL vs. SiriDB vs. Trafodion

System Properties Comparison GeoSpock vs. HBase vs. MySQL vs. SiriDB vs. Trafodion

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

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

Description

Spatial and temporal data processing engine for extreme data scale

Wide-column store based on Apache Hadoop and on concepts of BigTable

Widely used open source RDBMS

Open Source Time Series DBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Wide column store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

geospock.com

Technical documentation

hbase.apache.org/book.html

dev.mysql.com/doc

docs.siridb.com

trafodion.apache.org/documentation.html

Developer

GeoSpock

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

Apache Software Foundation, originally developed by HP

Initial release

2008

1995

2017

2014

Current release

2.0, September 2019

2.3.4, January 2021

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

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, Javascript

Java

C and C++

C++, Java

Server operating systems

hosted

Linux
Unix
Windows

using Cygwin

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free, schema definition possible

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

yes

Numeric data

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

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

Single row ACID (across millions of columns)

ACID

not for MyISAM storage engine

ACID

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

Access rights for users can be defined per table

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

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.