DBMS > LevelDB vs. Lovefield vs. searchxml vs. SQLite vs. Tkrzw

System Properties Comparison LevelDB vs. Lovefield vs. searchxml vs. SQLite vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

DBMS for structured and unstructured content wrapped with an application server

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

Key-value store

Relational DBMS

Native XML DBMS
Search engine

Relational DBMS

Key-value store

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

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

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

Website

github.com/google/leveldb

google.github.io/lovefield

www.searchxml.net/category/products

www.sqlite.org

dbmx.net/tkrzw

Technical documentation

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

github.com/google/lovefield/blob/master/docs/spec_index.md

www.searchxml.net/support/handouts

www.sqlite.org/docs.html

Developer

Google

informationpartners gmbh

Dwayne Richard Hipp

Mikio Hirabayashi

Initial release

2011

2014

2015

2000

2020

Current release

1.23, February 2021

2.1.12, February 2017

1.0

3.45.3 (15 April 2024), April 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache 2.0

commercial

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

C++

JavaScript

C++

Server operating systems

Illumos
Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Windows

server-less

Linux
macOS

Data scheme

schema-free

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

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript

C++

most other programming languages supported via APIs

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

on the application server

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

sychronisation to multiple collections

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

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

using specific database classes

User concepts

Access control

Domain, group and role-based access control at the document level and for application services

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.