DBMS > Apache Druid vs. H2GIS vs. MySQL vs. OpenEdge

System Properties Comparison Apache Druid vs. H2GIS vs. MySQL vs. OpenEdge

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Spatial extension of H2

Widely used open source RDBMS

Application development environment with integrated database management system

Primary database model

Relational DBMS
Time Series DBMS

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	3.45
Rank	#85	Overall
	#46	Relational DBMS

Website

druid.apache.org

www.h2gis.org

www.mysql.com

www.progress.com/openedge

Technical documentation

druid.apache.org/docs/latest/design

www.h2gis.org/docs/home

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

Developer

Apache Software Foundation and contributors

CNRS

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Initial release

2012

2013

1995

1984

Current release

29.0.1, April 2024

8.4.0, April 2024

OpenEdge 12.2, March 2020

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

LGPL 3.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Server operating systems

Linux
OS X
Unix

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-less columns are supported

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

SQL for querying

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

JDBC
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Java

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

Progress proprietary ABL (Advanced Business Language)

Server-side scripts

Stored procedures

yes

based on H2

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes

based on H2

Multi-source replication
Source-replica 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

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

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

yes

based on H2

Users with fine-grained authorization concept

no user groups or roles

Users and groups

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.