DBMS > LevelDB vs. Lovefield vs. MarkLogic vs. SQLite

System Properties Comparison LevelDB vs. Lovefield vs. MarkLogic vs. SQLite

Please select another system to include it in the comparison.

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

Operational and transactional Enterprise NoSQL database

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

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

Score	2.75
Rank	#107	Overall
	#19	Key-value stores

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	6.50
Rank	#56	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#5	Search engines

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/google/leveldb

google.github.io/lovefield

www.marklogic.com

www.sqlite.org

Technical documentation

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

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

docs.marklogic.com

www.sqlite.org/docs.html

Developer

Google

MarkLogic Corp.

Dwayne Richard Hipp

Initial release

2011

2014

2001

2000

Current release

1.23, February 2021

2.1.12, February 2017

11.0, December 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

BSD

Open Source

Apache 2.0

commercial

restricted free version is 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

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

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

schema-free

Schema can be enforced

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
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
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

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

via XQuery or JavaScript

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

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.