DBMS > LevelDB vs. Linter vs. MySQL vs. SQream DB

System Properties Comparison LevelDB vs. Linter vs. MySQL vs. SQream DB

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

RDBMS for high security requirements

Widely used open source RDBMS

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Spatial DBMS

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.09
Rank	#346	Overall
	#152	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

github.com/google/leveldb

linter.ru

www.mysql.com

sqream.com

Technical documentation

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

dev.mysql.com/doc

docs.sqream.com

Developer

Google

relex.ru

Oracle

since 2010, originally MySQL AB, then Sun

SQream Technologies

Initial release

2011

1990

1995

2017

Current release

1.23, February 2021

8.4.0, April 2024

2022.1.6, December 2022

License

Commercial or Open Source

Open Source

BSD

commercial

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.

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

C++, CUDA, Haskell, Java, Scala

Server operating systems

Illumos
Linux
OS X
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

.Net
JDBC
ODBC

Supported programming languages

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Multi-source replication
Source-replica replication

none

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

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

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.