DBMS > Amazon DocumentDB vs. LMDB vs. OrientDB vs. Prometheus vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. LMDB vs. OrientDB vs. Prometheus vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

Multi-model DBMS (Document, Graph, Key/Value)

Open-source Time Series DBMS and monitoring system

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

Primary database model

Document store

Key-value store

Document store
Graph DBMS
Key-value store

Time Series DBMS

Relational DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

aws.amazon.com/documentdb

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

orientdb.org

prometheus.io

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

www.lmdb.tech/doc

www.orientdb.com/docs/last/index.html

prometheus.io/docs

docs.snowflake.net/manuals/index.html

Developer

Symas

OrientDB LTD; CallidusCloud; SAP

Snowflake Computing Inc.

Initial release

2019

2011

2010

2015

2014

Current release

0.9.32, January 2024

3.2.29, March 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache 2.0

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.

Implementation language

Java

Server operating systems

hosted

Linux
Unix
Windows

All OS with a Java JDK (>= JDK 6)

Linux
Windows

hosted

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

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

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

.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
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java, Javascript

user defined functions

Triggers

Hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

none

Multi-source replication

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

relationship in graphs

yes

Transaction concepts

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

Atomic single-document operations

ACID

Concurrency

Support for concurrent manipulation of data

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

User concepts

Access control

Access rights for users and roles

Access rights for users and roles; record level security configurable

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

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.