DBMS > H2GIS vs. LevelDB vs. MySQL vs. OushuDB vs. PostGIS

System Properties Comparison H2GIS vs. LevelDB vs. MySQL vs. OushuDB vs. PostGIS

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

Spatial extension of PostgreSQL

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.04
Rank	#363	Overall
	#154	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.h2gis.org

github.com/google/leveldb

www.mysql.com

www.oushu.com/product/oushuDB

postgis.net

Technical documentation

www.h2gis.org/docs/home

github.com/google/leveldb/blob/main/doc/index.md

dev.mysql.com/doc

www.oushu.com/documentation

postgis.net/documentation

Developer

CNRS

Google

Oracle

since 2010, originally MySQL AB, then Sun

Oushu

Initial release

2013

2011

1995

2005

Current release

1.23, February 2021

8.4.0, April 2024

4.0.1, August 2020

3.4.2, February 2024

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL v2.0

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

C and C++

Server operating systems

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

Full-featured ANSI SQL support

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C
C++

Server-side scripts

Stored procedures

yes

based on H2

yes

proprietary syntax

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

none

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

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

with automatic compression on writes

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

Users with fine-grained authorization concept

no user groups or roles

Kerberos, SSL and role based access

yes

based on PostgreSQL

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.