DBMS > MarkLogic vs. RocksDB vs. Sphinx vs. Warp 10

System Properties Comparison MarkLogic vs. RocksDB vs. Sphinx vs. Warp 10

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Operational and transactional Enterprise NoSQL database

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

Open source search engine for searching in data from different sources, e.g. relational databases

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

Search engine

Time Series DBMS

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

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	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

Technical documentation

docs.marklogic.com

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

MarkLogic Corp.

Facebook, Inc.

Sphinx Technologies Inc.

SenX

Initial release

2001

2013

2001

2015

Current release

11.0, December 2022

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

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

Linux
OS X
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

schema-free

Schema can be enforced

schema-free

yes

schema-free

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

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL92

SQL-like query language (SphinxQL)

APIs and other access methods

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

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

yes

In-memory capabilities

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

yes, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.