DBMS > LMDB vs. Microsoft Azure Cosmos DB vs. RavenDB vs. VoltDB

System Properties Comparison LMDB vs. Microsoft Azure Cosmos DB vs. RavenDB vs. VoltDB

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

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Relational DBMS

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

azure.microsoft.com/services/cosmos-db

ravendb.net

www.voltdb.com

Technical documentation

www.lmdb.tech/doc

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

docs.voltdb.com

Developer

Symas

Microsoft

Hibernating Rhinos

VoltDB Inc.

Initial release

2011

2014

2010

Current release

0.9.32, January 2024

5.4, July 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

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

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.

Implementation language

Java, C++

Server operating systems

Linux
Unix
Windows

hosted

Linux
macOS
Raspberry Pi
Windows

Linux
OS X

for development

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

yes

only a subset of SQL 99

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Java API
JDBC
RESTful HTTP/JSON API

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
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

JavaScript

yes

Java

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Implicit feature of the cloud service

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

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

User concepts

Access control

Access rights can be defined down to the item level

Authorization levels configured per client per database

Users and roles with access to stored procedures

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.