DBMS > H2 vs. Hazelcast vs. SQLite vs. Tigris

System Properties Comparison H2 vs. Hazelcast vs. SQLite vs. Tigris

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.

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Key-value store

Relational DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Spatial DBMS

Document store

JSON support with IMDG 3.12

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

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

Technical documentation

www.h2database.com/html/main.html

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

www.tigrisdata.com/docs

Developer

Thomas Mueller

Hazelcast

Dwayne Richard Hipp

Tigris Data, Inc.

Initial release

2005

2008

2000

2022

Current release

2.2.220, July 2023

5.3.6, November 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

Open Source

Apache Version 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

Java

Server operating systems

All OS with a Java VM

server-less

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Java

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
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

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

yes

Event Listeners, Executor Services

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

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

Replicated Map

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control

Access rights for users and roles

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.