DBMS > Apache Solr vs. LMDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Apache Solr vs. LMDB vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely used distributed, scalable search engine based on Apache Lucene

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

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Search engine

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	34.15
Rank	#24	Overall
	#3	Search engines

Score	1.94
Rank	#120	Overall
	#20	Key-value stores

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

Website

solr.apache.org

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

azure.microsoft.com/services/cosmos-db

Technical documentation

solr.apache.org/resources.html

www.lmdb.tech/doc

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Symas

Microsoft

Initial release

2006

2011

2014

Current release

9.6.1, May 2024

0.9.32, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
Unix
Windows

hosted

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

yes

JSON types

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

All search fields are automatically indexed

yes

All properties auto-indexed by default

SQL

Support of SQL

Solr Parallel SQL Interface

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP/JSON API

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

Supported programming languages

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

Java plugins

JavaScript

Triggers

yes

User configurable commands triggered on index changes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

optimistic locking

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

yes

Access rights can be defined down to the item level

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.