DBMS > LeanXcale vs. LevelDB vs. MySQL vs. UniData,UniVerse

System Properties Comparison LeanXcale vs. LevelDB vs. MySQL vs. UniData,UniVerse

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Widely used open source RDBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Multivalue DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.28
Rank	#286	Overall
	#41	Key-value stores
	#130	Relational DBMS

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

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.25
Rank	#112	Overall
	#2	Multivalue DBMS

Website

www.leanxcale.com

github.com/google/leveldb

www.mysql.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

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

dev.mysql.com/doc

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

LeanXcale

Google

Oracle

since 2010, originally MySQL AB, then Sun

Rocket Software

Initial release

2015

2011

1995

1985

Current release

1.23, February 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

Server operating systems

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

optional

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

yes

through Apache Derby

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
ODBC
Proprietary native API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

C
Java
Scala

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

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

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

configurable

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

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights according to SQL-standard and operating system based

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.