DBMS > Oracle NoSQL vs. Riak TS vs. RocksDB vs. Rockset

System Properties Comparison Oracle NoSQL vs. Riak TS vs. RocksDB vs. Rockset

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

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Document store
Key-value store
Relational DBMS

Time Series DBMS

Key-value store

Document store

Secondary database models

Relational DBMS
Search engine

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	0.28
Rank	#307	Overall
	#27	Time Series DBMS

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

Score	0.82
Rank	#212	Overall
	#36	Document stores

Website

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

rocksdb.org

rockset.com

Technical documentation

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

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

github.com/facebook/rocksdb/wiki

docs.rockset.com

Developer

Oracle

Open Source, formerly Basho Technologies

Facebook, Inc.

Rockset

Initial release

2011

2015

2013

2019

Current release

24.1, May 2024

3.0.0, September 2022

9.2.1, May 2024

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

commercial

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

Java

Erlang

C++

Server operating systems

Linux
Solaris SPARC/x86

Linux
OS X

Linux

hosted

Data scheme

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

schema-free

Typing

predefined data types such as float or date

optional

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

restricted

all fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes, limited

Read-only SQL queries, including JOINs

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

HTTP REST

Supported programming languages

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

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Automatic sharding

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

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

configurable

ACID within a storage node (=shard)

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights for users and organizations can be defined via Rockset console

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.