DBMS > LevelDB vs. OrigoDB vs. Riak TS vs. SQLite vs. XTDB

System Properties Comparison LevelDB vs. OrigoDB vs. Riak TS vs. SQLite vs. XTDB

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

A fully ACID in-memory object graph database

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Widely used embeddable, in-process RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Document store
Object oriented DBMS

Time Series DBMS

Relational DBMS

Document 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.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/google/leveldb

origodb.com

www.sqlite.org

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

origodb.com/docs

www.tiot.jp/riak-docs/riak/ts/latest

www.sqlite.org/docs.html

www.xtdb.com/docs

Developer

Google

Robert Friberg et al

Open Source, formerly Basho Technologies

Dwayne Richard Hipp

Juxt Ltd.

Initial release

2011

2009

under the name LiveDB

2015

2000

2019

Current release

1.23, February 2021

3.0.0, September 2022

3.45.3 (15 April 2024), April 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

BSD

Open Source

Public Domain

Open Source

MIT License

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++

Erlang

Clojure

Server operating systems

Illumos
Linux
OS X
Windows

Linux
Windows

Linux
OS X

server-less

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

yes, extensible-data-notation format

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.

can be achieved using .NET

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes, limited

yes

SQL-92 is not fully supported

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP API
Native Erlang Interface

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP REST
JDBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

Clojure
Java

Server-side scripts

Stored procedures

yes

Erlang

Triggers

yes

Domain Events

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

selectable replication factor

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

depending on model

links between datasets can be stored

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

Write ahead log

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Role based authorization

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.