DBMS > Dolt vs. GeoMesa vs. H2 vs. HyperSQL vs. Warp 10

System Properties Comparison Dolt vs. GeoMesa vs. H2 vs. HyperSQL vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store

Spatial DBMS

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	7.57
Rank	#47	Overall
	#30	Relational DBMS

Score	3.14
Rank	#85	Overall
	#46	Relational DBMS

Score	0.06
Rank	#351	Overall
	#35	Time Series DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

Technical documentation

docs.dolthub.com

www.geomesa.org/documentation/stable/user/index.html

www.h2database.com/html/main.html

hsqldb.org/web/hsqlDocsFrame.html

www.warp10.io/content/02_Getting_started

Developer

DoltHub Inc

CCRi and others

Thomas Mueller

SenX

Initial release

2018

2014

2005

2001

2015

Current release

5.0.1, July 2024

2.2.220, July 2023

2.7.2, June 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

based on BSD license

Open Source

Apache License 2.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.

Implementation language

Scala

Java

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Linux
OS X
Windows

Data scheme

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

CLI Client
HTTP REST

JDBC
ODBC

HTTP API

JDBC via HTTP
JDBC
ODBC

HTTP API
Jupyter
WebSocket

Supported programming languages

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

Java

All languages supporting JDBC/ODBC
Java

Server-side scripts

Stored procedures

yes

currently in alpha release

Java Stored Procedures and User-Defined Functions

Java, SQL

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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.

depending on storage layer

yes

User concepts

Access control

Only one user is configurable, and must be specified in the config file at startup

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

25 Hot New Data Tools and What They DON’T Do
14 May 2020, Towards Data Science

Solve your MLOps Problems with an Open Source Data Science Stack
2 June 2021, Towards Data Science

provided by Google News

HyperSQL DataBase flaw leaves library vulnerable to RCE
24 October 2022, The Daily Swig

Introduction to JDBC with HSQLDB tutorial
14 November 2022, TheServerSide.com

provided by Google News

Launched Just A Year Ago, Open-Source Scality S3 Server Gains Extraordinary Momentum As It Simplifies The Life Of Developers
28 June 2017, PR Newswire

provided by Google News

Share this page