DBMS > Apache Impala vs. LMDB vs. Machbase Neo vs. MySQL vs. STSdb

System Properties Comparison Apache Impala vs. LMDB vs. Machbase Neo vs. MySQL vs. STSdb

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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

TimeSeries DBMS for AIoT and BigData

Widely used open source RDBMS

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

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

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

impala.apache.org

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

machbase.com

www.mysql.com

github.com/STSSoft/STSdb4

Technical documentation

impala.apache.org/impala-docs.html

www.lmdb.tech/doc

machbase.com/dbms

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Symas

Machbase

Oracle

since 2010, originally MySQL AB, then Sun

STS Soft SC

Initial release

2013

2011

2013

1995

2011

Current release

4.1.0, June 2022

0.9.32, January 2024

V8.0, August 2023

8.4.0, April 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

commercial

free test version available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPLv2, commercial license available

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

Server operating systems

Linux

Linux
Unix
Windows

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

SQL-like DML and DDL statements

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API

Supported programming languages

All languages supporting JDBC/ODBC

.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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

C#
Java

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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

volatile and lookup table

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

simple password-based access control

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.