DBMS > Drizzle vs. H2GIS vs. Hyprcubd vs. MySQL vs. TinkerGraph

System Properties Comparison Drizzle vs. H2GIS vs. Hyprcubd vs. MySQL vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Spatial extension of H2

Serverless Time Series DBMS

Widely used open source RDBMS

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.05
Rank	#372	Overall
	#7	Spatial DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

www.h2gis.org

hyprcubd.com (offline)

www.mysql.com

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

www.h2gis.org/docs/home

dev.mysql.com/doc

Developer

Drizzle project, originally started by Brian Aker

CNRS

Hyprcubd, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2008

2013

1995

2009

Current release

7.2.4, September 2012

8.3.0, January 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

LGPL 3.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

C++

Java

C and C++

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC

gRPC (https)

ADO.NET
JDBC
ODBC
Proprietary native API

TinkerPop 3

Supported programming languages

C
C++
Java
PHP

Java

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

Groovy
Java

Server-side scripts

Stored procedures

yes

based on H2

yes

proprietary syntax

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on H2

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

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

Durability

Support for making data persistent

yes

optional

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

based on H2

token access

Users with fine-grained authorization concept

no user groups or roles

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.