DBMS > IBM Db2 warehouse vs. MarkLogic vs. RocksDB vs. Solr vs. Tigris

System Properties Comparison IBM Db2 warehouse vs. MarkLogic vs. RocksDB vs. Solr vs. Tigris

Editorial information provided by DB-Engines

Name

Description

Cloud-based data warehousing service

Operational and transactional Enterprise NoSQL database

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

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

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Search engine

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	1.30
Rank	#164	Overall
	#75	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

www.ibm.com/products/db2/warehouse

Technical documentation

docs.marklogic.com

github.com/facebook/rocksdb/wiki

solr.apache.org/resources.html

www.tigrisdata.com/docs

Developer

IBM

MarkLogic Corp.

Facebook, Inc.

Apache Software Foundation

Tigris Data, Inc.

Initial release

2014

2001

2013

2006

2022

Current release

11.0, December 2022

8.11.4, April 2024

9.6.0, April 2024

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD

Open Source

Apache Version 2

Open Source

Apache Version 2.0

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

C++

Java

Server operating systems

hosted

Linux
OS X
Windows

Linux

All OS with a Java VM

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

Linux
macOS
Windows

Data scheme

yes

schema-free

Schema can be enforced

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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/export of XML data possible

yes

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL92

Solr Parallel SQL Interface

APIs and other access methods

.NET Client API
JDBC
ODBC
OLE DB

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

C++ API
Java API

Java API
RESTful HTTP/JSON API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

PL/SQL, SQL PL

yes

via XQuery or JavaScript

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

yes

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, with Range Indexes

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

yes

Access rights for users and 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.