DBMS > Apache Druid vs. BaseX vs. NSDb vs. RocksDB vs. Sphinx

System Properties Comparison Apache Druid vs. BaseX vs. NSDb vs. RocksDB vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

Light-weight Native XML DBMS with support for XQuery 3.0 and interactive GUI.

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Primary database model

Relational DBMS
Time Series DBMS

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

Score	3.29
Rank	#95	Overall
	#49	Relational DBMS
	#7	Time Series DBMS

Score	1.90
Rank	#136	Overall
	#4	Native XML DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

Technical documentation

druid.apache.org/docs/latest/design

docs.basex.org

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Apache Software Foundation and contributors

BaseX GmbH

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2012

2007

2017

2013

2001

Current release

29.0.1, April 2024

10.7, August 2023

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

BSD license

Open Source

Apache Version 2.0

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

Java

Java, Scala

C++

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

Linux
macOS

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

Typing

predefined data types such as float or date

yes

XQuery supports types

yes: int, bigint, decimal, string

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.

Secondary indexes

yes

all fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

SQL for querying

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
RESTful HTTP/JSON API

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

gRPC
HTTP REST
WebSocket

C++ API
Java API

Proprietary protocol

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

Actionscript
C
C#
Haskell
Java
JavaScript

Node.js
Lisp
Perl
PHP
Python
Qt
Rebol
Ruby
Scala
Visual Basic

Java
Scala

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

Triggers

yes

via events

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

none

Sharding

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

multiple readers, single writer

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

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

In-memory capabilities

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

yes

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Users with fine-grained authorization concept on 4 levels

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.