DBMS > LevelDB vs. Transbase vs. Vitess vs. XTDB

System Properties Comparison LevelDB vs. Transbase vs. Vitess 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 resource-optimized, high-performance, universally applicable RDBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Primary database model

Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

github.com/google/leveldb

www.transaction.de/en/products/transbase.html

vitess.io

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

Technical documentation

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

www.transaction.de/en/products/transbase/features.html

vitess.io/docs

www.xtdb.com/docs

Developer

Google

Transaction Software GmbH

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

2011

1987

2013

2019

Current release

1.23, February 2021

Transbase 8.3, 2022

15.0.2, December 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

BSD

commercial

free development license

Open Source

Apache Version 2.0, commercial licenses available

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

C and C++

Clojure

Server operating systems

Illumos
Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Docker
Linux
macOS

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

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

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

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.

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

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page