DBMS > Altibase vs. OrigoDB vs. RDF4J vs. RocksDB vs. VoltDB

System Properties Comparison Altibase vs. OrigoDB vs. RDF4J vs. RocksDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

A fully ACID in-memory object graph database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

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

Relational DBMS

Document store
Object oriented DBMS

RDF store

Key-value store

Relational DBMS

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

Score	1.07
Rank	#186	Overall
	#87	Relational DBMS

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

Score	0.69
Rank	#230	Overall
	#9	RDF stores

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

origodb.com/docs

rdf4j.org/documentation

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Altibase

Robert Friberg et al

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Facebook, Inc.

VoltDB Inc.

Initial release

1999

2009

under the name LiveDB

2004

2013

2010

Current release

v7.3, 2023, August 2023

9.2.1, May 2024

11.3, April 2022

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

BSD

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

Java

C++

Java, C++

Server operating systems

AIX
HP-UX
Linux

Linux
Windows

Linux
OS X
Unix
Windows

Linux

Linux
OS X

for development

Data scheme

yes

RDF Schemas

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
Proprietary protocol

.NET Client API
HTTP API
LINQ

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C
C++
Java

.Net

Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

Java

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

yes

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

yes

depending on model

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Isolation support depends on the API used

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

in-memory storage is supported as well

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

fine grained access rights according to SQL-standard

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.