DBMS > LMDB vs. Microsoft Azure SQL Database vs. MySQL vs. Tibero

System Properties Comparison LMDB vs. Microsoft Azure SQL Database vs. MySQL vs. Tibero

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performant, light-weight, embedded key-value database library

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.99
Rank	#125	Overall
	#21	Key-value stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.symas.com/symas-embedded-database-lmdb

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

us.tmaxsoft.com/products/tibero

Technical documentation

www.lmdb.tech/doc

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

Symas

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

TmaxSoft

Initial release

2011

2010

1995

2003

Current release

0.9.32, January 2024

V12

8.4.0, April 2024

6, April 2015

License

Commercial or Open Source

Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Cloud-based only

Only available as a cloud service

yes

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 and Assembler

Server operating systems

Linux
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

Transact SQL

yes

proprietary syntax

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

by range, hash, list or composite

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, with always 3 replicas available

Multi-source 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

yes

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

In-memory capabilities

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

yes

planned for next version

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.