DBMS > Derby vs. Machbase Neo vs. OrigoDB vs. RocksDB vs. SpatiaLite

System Properties Comparison Derby vs. Machbase Neo vs. OrigoDB vs. RocksDB vs. SpatiaLite

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.

TimeSeries DBMS for AIoT and BigData

A fully ACID in-memory object graph database

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

Spatial extension of SQLite

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Key-value store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

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

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

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

machbase.com/dbms

origodb.com/docs

github.com/facebook/rocksdb/wiki

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Apache Software Foundation

Machbase

Robert Friberg et al

Facebook, Inc.

Alessandro Furieri

Initial release

1997

2013

2009

under the name LiveDB

2013

2008

Current release

10.17.1.0, November 2023

V8.0, August 2023

9.2.1, May 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache version 2

commercial

free test version available

Open Source

BSD

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

Server operating systems

All OS with a Java VM

Linux
macOS
Windows

Linux
Windows

Linux

server-less

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

JDBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

Java

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Source-replica replication

yes

none

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

yes

depending on model

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

simple password-based access control

Role based authorization

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.