DBMS > Altibase vs. MySQL vs. OrigoDB vs. RisingWave

System Properties Comparison Altibase vs. MySQL vs. OrigoDB vs. RisingWave

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

Widely used open source RDBMS

A fully ACID in-memory object graph database

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.87
Rank	#200	Overall
	#93	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.61
Rank	#237	Overall
	#111	Relational DBMS

Website

altibase.com

www.mysql.com

origodb.com

www.risingwave.com/database

Technical documentation

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

dev.mysql.com/doc

origodb.com/docs

docs.risingwave.com/docs/current/intro

Developer

Altibase

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

RisingWave Labs

Initial release

1999

1995

2009

under the name LiveDB

2022

Current release

v7.3, 2023, August 2023

9.0.0, July 2024

1.2, September 2023

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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

Rust

Server operating systems

AIX
HP-UX
Linux

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

Standard SQL-types and JSON

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

JDBC
PostgreSQL wire protocol

Supported programming languages

C
C++
Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

proprietary syntax

yes

UDFs in Python or Java

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica 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

not for MyISAM storage engine

depending on model

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.