DBMS > Oracle NoSQL vs. RocksDB vs. TerminusDB vs. YottaDB

System Properties Comparison Oracle NoSQL vs. RocksDB vs. TerminusDB vs. YottaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

A fast and solid embedded Key-value store

Primary database model

Document store
Key-value store
Relational DBMS

Key-value store

Graph DBMS

Key-value store

Secondary database models

Document store
RDF store

Relational DBMS

using the Octo plugin

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

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

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

www.oracle.com/database/nosql/technologies/nosql

rocksdb.org

terminusdb.com

yottadb.com

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

yottadb.com/resources/documentation

Developer

Oracle

Facebook, Inc.

DataChemist Ltd.

YottaDB, LLC

Initial release

2011

2013

2018

2001

Current release

23.3, December 2023

9.2.1, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD

Open Source

GPL V3

Open Source

AGPL 3.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

Java

C++

Prolog, Rust

Server operating systems

Linux
Solaris SPARC/x86

Linux

Docker
Linux

Data scheme

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

yes

schema-free

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language (WOQL)

by using the Octo plugin

APIs and other access methods

RESTful HTTP API

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Journaling Streams

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

yes

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

yes

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

Access rights for users and roles

Role-based access control

Users and groups based on OS-security mechanisms

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.