DBMS > OrigoDB vs. RocksDB vs. SpatiaLite vs. TerminusDB

System Properties Comparison OrigoDB vs. RocksDB vs. SpatiaLite vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A fully ACID in-memory object graph database

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

Spatial extension of SQLite

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

Primary database model

Document store
Object oriented DBMS

Key-value store

Spatial DBMS

Graph DBMS

Secondary database models

Relational DBMS

Document store
RDF store

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

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

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

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

origodb.com

rocksdb.org

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

terminusdb.com

Technical documentation

origodb.com/docs

github.com/facebook/rocksdb/wiki

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

terminusdb.github.io/terminusdb/#

Developer

Robert Friberg et al

Facebook, Inc.

Alessandro Furieri

DataChemist Ltd.

Initial release

2009

under the name LiveDB

2013

2008

2018

Current release

9.2.1, May 2024

5.0.0, August 2020

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSD

Open Source

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

Open Source

GPL V3

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

C++

Prolog, Rust

Server operating systems

Linux
Windows

Linux

server-less

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

.NET Client API
HTTP API
LINQ

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Foreign keys

Referential integrity

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 journaling

In-memory capabilities

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

yes

User concepts

Access control

Role based authorization

Role-based access control

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.