DBMS > LevelDB vs. SingleStore vs. SQLite vs. Tkrzw

System Properties Comparison LevelDB vs. SingleStore vs. SQLite vs. Tkrzw

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

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

Key-value store

Secondary database models

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

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

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

github.com/google/leveldb

www.singlestore.com

www.sqlite.org

dbmx.net/tkrzw

Technical documentation

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

docs.singlestore.com

www.sqlite.org/docs.html

Developer

Google

SingleStore Inc.

Dwayne Richard Hipp

Mikio Hirabayashi

Initial release

2011

2013

2000

2020

Current release

1.23, February 2021

8.5, January 2024

3.46.1 (13 August 2024), August 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

BSD

commercial

free developer edition 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

C++

C++, Go

C++

Server operating systems

Illumos
Linux
OS X
Windows

Linux

64 bit version required

server-less

Linux
macOS

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

yes

but no triggers and foreign keys

yes

SQL-92 is not fully supported

APIs and other access methods

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

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

Bash
C
C#
Java
JavaScript (Node.js)
Python

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

hash partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

stores two copies of each physical data partition on two separate nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

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

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

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

Fine grained access control via users, groups 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.