DBMS > OrigoDB vs. Realm vs. RocksDB vs. VoltDB

System Properties Comparison OrigoDB vs. Realm vs. RocksDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

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)

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

Document store
Object oriented DBMS

Document store

Key-value store

Relational DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

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

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

Technical documentation

origodb.com/docs

realm.io/docs

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Robert Friberg et al

Realm, acquired by MongoDB in May 2019

Facebook, Inc.

VoltDB Inc.

Initial release

2009

under the name LiveDB

2014

2013

2010

Current release

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

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

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

Linux
Windows

Android
Backend: server-less
iOS
Windows

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

.NET Client API
HTTP API
LINQ

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net

.Net
Java

with Android only
Objective-C
React Native
Swift

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

yes

runs within the applications so server-side scripts are unnecessary

Java

Triggers

yes

Domain Events

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

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

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

yes

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.