DBMS > Apache Phoenix vs. BoltDB vs. RocksDB vs. Sphinx

System Properties Comparison Apache Phoenix vs. BoltDB vs. RocksDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

An embedded key-value store for Go.

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

Key-value store

Search engine

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

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

phoenix.apache.org

github.com/boltdb/bolt

rocksdb.org

sphinxsearch.com

Technical documentation

phoenix.apache.org

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Apache Software Foundation

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2014

2013

2001

Current release

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

9.2.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MIT License

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

C++

Server operating systems

Linux
Unix
Windows

BSD
Linux
OS X
Solaris
Windows

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

yes

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

C++ API
Java API

Proprietary protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
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

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

none

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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.

In-memory capabilities

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

yes

User concepts

Access control

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

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.