DBMS > H2GIS vs. LevelDB vs. Oracle Berkeley DB vs. SQLite vs. Tkrzw

System Properties Comparison H2GIS vs. LevelDB vs. Oracle Berkeley DB vs. SQLite vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Spatial extension of H2

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used in-process key-value store

Widely used embeddable, in-process RDBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Spatial DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Relational DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.h2gis.org

github.com/google/leveldb

www.oracle.com/database/technologies/related/berkeleydb.html

www.sqlite.org

dbmx.net/tkrzw

Technical documentation

www.h2gis.org/docs/home

github.com/google/leveldb/blob/main/doc/index.md

docs.oracle.com/cd/E17076_05/html/index.html

www.sqlite.org/docs.html

Developer

CNRS

Google

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Dwayne Richard Hipp

Mikio Hirabayashi

Initial release

2013

2011

1994

2000

2020

Current release

1.23, February 2021

18.1.40, May 2020

3.46.0 (23 May 2024), May 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

LGPL 3.0

Open Source

BSD

Open Source

commercial license 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

C++

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

Illumos
Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

server-less

Linux
macOS

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

based on H2

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

none

Source-replica replication

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, multi-version concurrency control (MVCC)

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

yes

based on H2

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.