DBMS > LevelDB vs. OrigoDB vs. VoltDB vs. XTDB

System Properties Comparison LevelDB vs. OrigoDB vs. VoltDB vs. XTDB

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

A fully ACID in-memory object graph database

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

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

Primary database model

Key-value store

Document store
Object oriented 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	1.44
Rank	#158	Overall
	#73	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/google/leveldb

origodb.com

www.voltdb.com

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

Technical documentation

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

origodb.com/docs

docs.voltdb.com

www.xtdb.com/docs

Developer

Google

Robert Friberg et al

VoltDB Inc.

Juxt Ltd.

Initial release

2011

2009

under the name LiveDB

2010

2019

Current release

1.23, February 2021

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Clojure

Server operating systems

Illumos
Linux
OS X
Windows

Linux
Windows

Linux
OS X

for development

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

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

SQL

Support of SQL

yes

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

.NET Client API
HTTP API
LINQ

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Domain Events

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

Multi-source replication
Source-replica replication

yes, each node contains all data

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

depending on model

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

Write ahead log

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

LevelDB in Ruby — SitePoint
22 October 2014, SitePoint

Microsoft Teams stores auth tokens as cleartext in Windows, Linux, Macs
14 September 2022, BleepingComputer

Pliops unveils XDP-Rocks for RocksDB – Blocks and Files
19 October 2022, Blocks & Files

XanMod, Liquorix Kernels Offer Some Advantages On AMD Ryzen 5 Notebook
26 July 2021, Phoronix

Rust-Based Info Stealers Abuse GitHub Codespaces
19 May 2023, Trend Micro

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page