DBMS > BoltDB vs. OrientDB vs. OrigoDB vs. Postgres-XL vs. RocksDB

System Properties Comparison BoltDB vs. OrientDB vs. OrigoDB vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Multi-model DBMS (Document, Graph, Key/Value)

A fully ACID in-memory object graph database

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Key-value store

Document store
Graph DBMS
Key-value store

Document store
Object oriented DBMS

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

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

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

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

Website

github.com/boltdb/bolt

Technical documentation

www.orientdb.com/docs/last/index.html

origodb.com/docs

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

OrientDB LTD; CallidusCloud; SAP

Robert Friberg et al

Facebook, Inc.

Initial release

2013

2010

2009

under the name LiveDB

2014

since 2012, originally named StormDB

2013

Current release

3.2.29, March 2024

10 R1, October 2018

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

Mozilla public license

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

Linux
Windows

Linux
macOS

Linux

Data scheme

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

schema-free

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.

can be achieved using .NET

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language, no joins

yes

distributed, parallel query execution

APIs and other access methods

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Supported programming languages

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java, Javascript

yes

user defined functions

Triggers

Hooks

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

depending on model

yes

Transaction concepts

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

yes

ACID

MVCC

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

Access rights for users and roles; record level security configurable

Role based authorization

fine grained access rights according to SQL-standard

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.