DBMS > LevelDB vs. MySQL vs. Oracle NoSQL vs. Vertica vs. VoltDB

System Properties Comparison LevelDB vs. MySQL vs. Oracle NoSQL vs. Vertica vs. VoltDB

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

Widely used open source RDBMS

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

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

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Relational DBMS

Column oriented

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS
Time Series DBMS

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

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	10.06
Rank	#42	Overall
	#26	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/google/leveldb

www.mysql.com

www.oracle.com/database/nosql/technologies/nosql

www.vertica.com

www.voltdb.com

Technical documentation

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

dev.mysql.com/doc

docs.oracle.com/en/database/other-databases/nosql-database/index.html

vertica.com/documentation

docs.voltdb.com

Developer

Google

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

OpenText

previously Micro Focus and Hewlett Packard

VoltDB Inc.

Initial release

2011

1995

2011

2005

2010

Current release

1.23, February 2021

8.4.0, April 2024

24.1, May 2024

12.0.3, January 2023

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Limited community edition free

Open Source

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

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

C and C++

Java

C++

Java, C++

Server operating systems

Illumos
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

Linux

Linux
OS X

for development

Data scheme

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

yes

Typing

predefined data types such as float or date

yes

optional

yes

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like DML and DDL statements

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

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

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

yes, PostgreSQL PL/pgSQL, with minor differences

Java

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

horizontal partitioning, hierarchical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

configurable

ACID within a storage node (=shard)

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

with automatic compression on writes

yes

Snapshots and command logging

In-memory capabilities

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

yes

off heap cache

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.