DBMS > RocksDB vs. Sadas Engine vs. Sphinx vs. VictoriaMetrics

System Properties Comparison RocksDB vs. Sadas Engine vs. Sphinx vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

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

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

Technical documentation

github.com/facebook/rocksdb/wiki

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

sphinxsearch.com/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Facebook, Inc.

SADAS s.r.l.

Sphinx Technologies Inc.

VictoriaMetrics

Initial release

2013

2006

2001

2018

Current release

8.11.4, April 2024

8.0

3.5.1, February 2023

v1.91, May 2023

License

Commercial or Open Source

Open Source

BSD

commercial

free trial version available

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.

Implementation language

C++

Server operating systems

Linux

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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

C++ API
Java API

JDBC
ODBC
Proprietary protocol

Proprietary protocol

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

none

Synchronous replication

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

yes

Transaction concepts

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

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

managed by 'Learn by Usage'

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

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.