DBMS > Realm vs. RocksDB vs. Sadas Engine vs. Sphinx vs. Vitess

System Properties Comparison Realm vs. RocksDB vs. Sadas Engine vs. Sphinx vs. Vitess

Editorial information provided by DB-Engines

Name

Description

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	7.60
Rank	#52	Overall
	#9	Document stores

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	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

Technical documentation

realm.io/docs

github.com/facebook/rocksdb/wiki

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

sphinxsearch.com/docs

vitess.io/docs

Developer

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

SADAS s.r.l.

Sphinx Technologies Inc.

The Linux Foundation, PlanetScale

Initial release

2014

2013

2006

2001

2013

Current release

8.11.4, April 2024

8.0

3.5.1, February 2023

15.0.2, December 2022

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, commercial licenses 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

C++

Server operating systems

Android
Backend: server-less
iOS
Windows

Linux

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Docker
Linux
macOS

Data scheme

yes

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

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

with proprietary extensions

APIs and other access methods

C++ API
Java API

JDBC
ODBC
Proprietary protocol

Proprietary protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
Java

with Android only
Objective-C
React Native
Swift

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

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

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

yes

proprietary syntax

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Multi-source replication
Source-replica 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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

In-Memory realm

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

yes

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

Users with fine-grained authorization concept

no user groups or 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.