DBMS > Apache Phoenix vs. BaseX vs. Elasticsearch vs. NSDb vs. RocksDB

System Properties Comparison Apache Phoenix vs. BaseX vs. Elasticsearch vs. NSDb vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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)

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.73
Rank	#142	Overall
	#4	Native XML DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

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

Website

phoenix.apache.org

basex.org

www.elastic.co/elasticsearch

nsdb.io

rocksdb.org

Technical documentation

phoenix.apache.org

docs.basex.org

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

nsdb.io/Architecture

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

BaseX GmbH

Elastic

Facebook, Inc.

Initial release

2014

2007

2010

2017

2013

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

10.7, August 2023

8.6, January 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD license

Open Source

Elastic License

Open Source

Apache Version 2.0

Open Source

BSD

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
Unix
Windows

Linux
OS X
Windows

All OS with a Java VM

Linux
macOS

Linux

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

Typing

predefined data types such as float or date

yes

XQuery supports types

yes

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 search fields are automatically indexed

all fields are automatically indexed

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

JDBC

Java API
RESTful HTTP API
RESTXQ
WebDAV
XML:DB
XQJ

Java API
RESTful HTTP/JSON API

gRPC
HTTP REST
WebSocket

C++ API
Java API

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

Actionscript
C
C#
Haskell
Java
JavaScript

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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

via events

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

multiple readers, single writer

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

In-memory capabilities

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

yes

Memcached and Redis integration

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.