DBMS > Microsoft Azure AI Search vs. Realm vs. Riak KV vs. RocksDB vs. VoltDB

System Properties Comparison Microsoft Azure AI Search vs. Realm vs. Riak KV vs. RocksDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Search-as-a-service for web and mobile app development

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

Distributed, fault tolerant key-value store

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Search engine

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Relational DBMS

Secondary database models

Vector DBMS

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

Score	5.59
Rank	#63	Overall
	#7	Search engines

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

azure.microsoft.com/en-us/services/search

realm.io

rocksdb.org

www.voltdb.com

Technical documentation

learn.microsoft.com/en-us/azure/search

realm.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Microsoft

Realm, acquired by MongoDB in May 2019

OpenSource, formerly Basho Technologies

Facebook, Inc.

VoltDB Inc.

Initial release

2015

2014

2009

2013

2010

Current release

3.2.0, December 2022

8.11.4, April 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

C++

Java, C++

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux
OS X

Linux

Linux
OS X

for development

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

restricted

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
Java
JavaScript
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

Erlang

Java

Triggers

yes

Change Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

no "single point of failure"

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

selectable replication factor

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

In-Memory realm

yes

User concepts

Access control

yes

using Azure authentication

yes

yes, using Riak Security

Users and roles with access to stored procedures

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.