DBMS > OrigoDB vs. RocksDB vs. STSdb vs. ToroDB

System Properties Comparison OrigoDB vs. RocksDB vs. STSdb vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A fully ACID in-memory object graph database

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store
Object oriented DBMS

Key-value store

Document store

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

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

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

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

origodb.com

rocksdb.org

github.com/STSSoft/STSdb4

github.com/torodb/server

Technical documentation

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

Robert Friberg et al

Facebook, Inc.

STS Soft SC

8Kdata

Initial release

2009

under the name LiveDB

2013

2011

2016

Current release

8.11.4, April 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

BSD

Open Source

GPLv2, commercial license available

Open Source

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

Java

Server operating systems

Linux
Windows

Linux

Windows

All OS with a Java 7 VM

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

primitive types and user defined types (classes)

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

.NET Client API
HTTP API
LINQ

C++ API
Java API

.NET Client API

Supported programming languages

.Net

C
C++
Go
Java
Perl
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

Access rights for users and roles

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.