DBMS > FatDB vs. H2GIS vs. HEAVY.AI vs. MySQL vs. SiriDB

System Properties Comparison FatDB vs. H2GIS vs. HEAVY.AI vs. MySQL vs. SiriDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Spatial extension of H2

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Widely used open source RDBMS

Open Source Time Series DBMS

Primary database model

Document store
Key-value store

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Relational DBMS

Spatial DBMS

Document store
Spatial DBMS

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

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Website

www.h2gis.org

github.com/heavyai/heavydb
www.heavy.ai

www.mysql.com

siridb.com

Technical documentation

www.h2gis.org/docs/home

docs.heavy.ai

dev.mysql.com/doc

docs.siridb.com

Developer

FatCloud

CNRS

HEAVY.AI, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Cesbit

Initial release

2012

2013

2016

1995

2017

Current release

5.10, January 2022

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MIT License

Cloud-based only

Only available as a cloud service

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 CUDA

C and C++

Server operating systems

Windows

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data

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

Via inetgration in SQL Server

yes

with proprietary extensions

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

JDBC
ODBC
Thrift
Vega

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API

Supported programming languages

Java

All languages supporting JDBC/ODBC/Thrift
Python

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

Server-side scripts

Stored procedures

yes

via applications

yes

based on H2

yes

proprietary syntax

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Round robin

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

based on H2

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

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

Can implement custom security layer via applications

yes

based on H2

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

simple rights management via user accounts

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.