DBMS > H2GIS vs. KeyDB vs. MySQL vs. PostGIS vs. TimesTen

System Properties Comparison H2GIS vs. KeyDB vs. MySQL vs. PostGIS vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used open source RDBMS

Spatial extension of PostgreSQL

In-Memory RDBMS compatible to Oracle

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Relational 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	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

www.h2gis.org

github.com/Snapchat/KeyDB
keydb.dev

www.mysql.com

postgis.net

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

www.h2gis.org/docs/home

docs.keydb.dev

dev.mysql.com/doc

postgis.net/documentation

docs.oracle.com/database/timesten-18.1

Developer

CNRS

EQ Alpha Technology Ltd.

Oracle

since 2010, originally MySQL AB, then Sun

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2013

2019

1995

2005

1998

Current release

8.4.0, April 2024

3.4.2, February 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

BSD-3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

commercial

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

Linux

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

Java

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

based on H2

Lua

yes

proprietary syntax

user defined functions

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

by means of logfiles and checkpoints

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

simple password-based access control and ACL

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

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.