DBMS > Altibase vs. OrigoDB vs. RavenDB vs. Transbase

System Properties Comparison Altibase vs. OrigoDB vs. RavenDB vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

A fully ACID in-memory object graph database

Open Source Operational and Transactional Enterprise NoSQL Document Database

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Document store

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	1.00
Rank	#194	Overall
	#91	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

altibase.com

origodb.com

ravendb.net

www.transaction.de/en/products/transbase.html

Technical documentation

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

origodb.com/docs

ravendb.net/docs

www.transaction.de/en/products/transbase/features.html

Developer

Altibase

Robert Friberg et al

Hibernating Rhinos

Transaction Software GmbH

Initial release

1999

2009

under the name LiveDB

2010

1987

Current release

v7.3, 2023, August 2023

5.4, July 2022

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

AGPL version 3, commercial license available

commercial

free development license

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

Server operating systems

AIX
HP-UX
Linux

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

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

SQL-like query language (RQL)

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

.NET Client API
HTTP API
LINQ

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java

.Net

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

Role based authorization

Authorization levels configured per client per database

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Altibase is Adopted for Presence Service to Provide User Information and Online Presence
8 April 2019, PR Newswire

Open-source DBMS becoming battleground of public cloud
17 May 2022, english.etnews.com

South Korean company to provide database solution to Mobicom
10 April 2020, UB Post

In-Memory Database Market Rapid Growth at Deep Value Price :Altibase Corporation, Amazon Web Services, Datastax ...
13 April 2024, Post Production Buyers Guide

In-memory OLAP Database Market Is Booming (CAGR of 24.95%) Worldwide | Terracotta, Altibase, Kognitio, Mcobject ...
26 October 2018, openPR

provided by Google News

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

provided by Google News

Share this page