DBMS > Hazelcast vs. LMDB vs. Snowflake vs. VoltDB

System Properties Comparison Hazelcast vs. LMDB vs. Snowflake vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

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

Cloud-based data warehousing service for structured and semi-structured data

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

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

hazelcast.com

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

www.snowflake.com

www.voltdb.com

Technical documentation

hazelcast.org/imdg/docs

www.lmdb.tech/doc

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

Hazelcast

Symas

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2008

2011

2014

2010

Current release

5.3.6, November 2023

0.9.32, January 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

commercial

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

Java, C++

Server operating systems

All OS with a Java VM

Linux
Unix
Windows

hosted

Linux
OS X

for development

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.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

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

Java

Triggers

yes

Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

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

Role-based access control

Users with fine-grained authorization concept, user roles and pluggable authentication

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.