DBMS > Drizzle vs. Graph Engine vs. H2 vs. SQLite

System Properties Comparison Drizzle vs. Graph Engine vs. H2 vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	8.22
Rank	#50	Overall
	#32	Relational DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.graphengine.io

www.h2database.com

www.sqlite.org

Technical documentation

www.graphengine.io/docs/manual

www.h2database.com/html/main.html

www.sqlite.org/docs.html

Developer

Drizzle project, originally started by Brian Aker

Microsoft

Thomas Mueller

Dwayne Richard Hipp

Initial release

2008

2010

2005

2000

Current release

7.2.4, September 2012

2.2.220, July 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

MIT License

Open Source

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

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

C++

.NET and C

Java

Server operating systems

FreeBSD
Linux
OS X

.NET

All OS with a Java VM

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

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

with proprietary extensions

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

RESTful HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Java
PHP

C#
C++
F#
Visual Basic

Java

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

yes

Java Stored Procedures and User-Defined Functions

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.