DBMS > H2 vs. HarperDB vs. Machbase Neo vs. SQLite

System Properties Comparison H2 vs. HarperDB vs. Machbase Neo vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

TimeSeries DBMS for AIoT and BigData

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

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

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.h2database.com/html/main.html

docs.harperdb.io/docs

machbase.com/dbms

www.sqlite.org/docs.html

Developer

Thomas Mueller

HarperDB

Machbase

Dwayne Richard Hipp

Initial release

2005

2017

2013

2000

Current release

2.2.220, July 2023

3.1, August 2021

V8.0, August 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

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

commercial

free community edition available

commercial

free test version available

Open Source

Public Domain

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

Java

Node.js

Server operating systems

All OS with a Java VM

Linux
OS X

Linux
macOS
Windows

server-less

Data scheme

yes

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

JSON data types

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like data manipulation statements

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

Custom Functions

since release 3.1

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

A table resides as a whole on one (or more) nodes in a cluster

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

yes

the nodes on which a table resides can be defined

selectable replication factor

none

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

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

simple password-based access control

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.