DBMS > BoltDB vs. MySQL vs. NSDb vs. Sphinx vs. Tigris

System Properties Comparison BoltDB vs. MySQL vs. NSDb vs. Sphinx vs. Tigris

Editorial information provided by DB-Engines

Name

Description

Widely used open source RDBMS

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

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

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

Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Search engine

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Website

github.com/boltdb/bolt

Technical documentation

dev.mysql.com/doc

nsdb.io/Architecture

sphinxsearch.com/docs

www.tigrisdata.com/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Sphinx Technologies Inc.

Tigris Data, Inc.

Initial release

2013

1995

2017

2001

2022

Current release

8.4.0, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

Open Source

GPL version 2, commercial licence available

Open Source

Apache Version 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java, Scala

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
macOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
HTTP REST
WebSocket

Proprietary protocol

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java
Scala

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

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

yes, using FoundationDB

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

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.