DBMS > OrigoDB vs. RocksDB vs. SpatiaLite vs. SQream DB vs. VoltDB

System Properties Comparison OrigoDB vs. RocksDB vs. SpatiaLite vs. SQream DB vs. VoltDB

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

a GPU-based, columnar RDBMS for big data analytics workloads

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Object oriented DBMS

Key-value store

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

origodb.com

rocksdb.org

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

sqream.com

www.voltdb.com

Technical documentation

origodb.com/docs

github.com/facebook/rocksdb/wiki

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

docs.sqream.com

docs.voltdb.com

Developer

Robert Friberg et al

Facebook, Inc.

Alessandro Furieri

SQream Technologies

VoltDB Inc.

Initial release

2009

under the name LiveDB

2013

2008

2017

2010

Current release

8.11.4, April 2024

5.0.0, August 2020

2022.1.6, December 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

BSD

Open Source

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

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++, CUDA, Haskell, Java, Scala

Java, C++

Server operating systems

Linux
Windows

Linux

server-less

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

User defined using .NET types and collections

yes

yes, ANSI Standard SQL Types

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

only a subset of SQL 99

APIs and other access methods

.NET Client API
HTTP API
LINQ

C++ API
Java API

.Net
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net

C
C++
Go
Java
Perl
Python
Ruby

C++
Java
JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

user defined functions in Python

Java

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

horizontal and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication
Source-replica replication

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

depending on model

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Write ahead log

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.