DBMS > Derby vs. IRONdb vs. NSDb vs. RavenDB vs. RocksDB

System Properties Comparison Derby vs. IRONdb vs. NSDb vs. RavenDB vs. RocksDB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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
	#41	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Website

db.apache.org/derby

www.circonus.com/solutions/time-series-database/

nsdb.io

ravendb.net

rocksdb.org

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

nsdb.io/Architecture

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Circonus LLC.

Hibernating Rhinos

Facebook, Inc.

Initial release

1997

2017

2010

2013

Current release

10.17.1.0, November 2023

V0.10.20, January 2018

5.4, July 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache Version 2.0

Open Source

AGPL version 3, commercial license available

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

Java, Scala

C++

Server operating systems

All OS with a Java VM

Linux

Linux
macOS

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

JDBC

HTTP API

gRPC
HTTP REST
WebSocket

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Java
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic, metric affinity per node

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

configurable replication factor, datacenter aware

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

Authorization levels configured per client per database

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.