DBMS > Microsoft Azure SQL Database vs. Realm vs. RocksDB vs. Splunk vs. VoltDB

System Properties Comparison Microsoft Azure SQL Database vs. Realm vs. RocksDB vs. Splunk vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering with high compatibility to Microsoft SQL Server

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)

Analytics Platform for Big Data

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

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

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

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

azure.microsoft.com/en-us/products/azure-sql/database

Technical documentation

docs.microsoft.com/en-us/azure/azure-sql

realm.io/docs

github.com/facebook/rocksdb/wiki

docs.splunk.com/Documentation/Splunk

docs.voltdb.com

Developer

Microsoft

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

Splunk Inc.

VoltDB Inc.

Initial release

2010

2014

2013

2003

2010

Current release

V12

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition available

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

C++

Java, C++

Server operating systems

hosted

Android
Backend: server-less
iOS
Windows

Linux

Linux
OS X
Solaris
Windows

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

C++ API
Java API

HTTP REST

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C++
Go
Java
Perl
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Transact SQL

runs within the applications so server-side scripts are unnecessary

yes

Java

Triggers

yes

Change Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with always 3 replicas available

none

yes

Multi-source replication

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

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

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

fine grained access rights according to SQL-standard

yes

Access rights for users and roles

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.