DBMS > Derby vs. JaguarDB vs. Riak KV vs. RocksDB

System Properties Comparison Derby vs. JaguarDB vs. Riak KV vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Performant, highly scalable DBMS for AI and IoT applications

Distributed, fault tolerant key-value store

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

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Key-value store

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

Key-value store

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

Score	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

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

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

Website

db.apache.org/derby

www.jaguardb.com

rocksdb.org

Technical documentation

db.apache.org/derby/manuals/index.html

www.jaguardb.com/support.html

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

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

DataJaguar, Inc.

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

1997

2015

2009

2013

Current release

10.17.1.0, November 2023

3.3 July 2023

3.2.0, December 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL V3.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

BSD

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++

the server part. Clients available in other languages

Erlang

C++

Server operating systems

All OS with a Java VM

Linux

Linux
OS X

Linux

Data scheme

yes

schema-free

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

restricted

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC

JDBC
ODBC

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Java

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

selectable replication factor

yes

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

links between data sets can be stored

Transaction concepts

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

ACID

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

User concepts

Access control

fine grained access rights according to SQL-standard

rights management via user accounts

yes, using Riak Security

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.