RonDB

OLTP

RonDB is a Key-Value store with SQL Capabilites, it is a fork of MySQL NDB Cluster.

Concurrency Control

Two-Phase Locking (Deadlock Detection)

RonDB uses strict two-phase locking when using locks. READ COMMITTED is lockless and always reads the latest committed value. READ COMMITTED is default from MySQL.

Data Model

Relational Key/Value

Fault Tolerance

Conflict Resolution Synchronous Replication Asynchronous Replication

Within one cluster, RonDB uses synchronous replication. For multi-region replication, RonDB supports both asynchronous active-passive and active-active (with conflict resolution) between clusters.

Foreign Keys

Supported

Indexes

Hash Table T-Tree

Isolation Levels

Read Committed Repeatable Read

By default, RonDB supports read committed. It can however also support the repeatable read mode by using SELECT ... LOCK IN SHARED MODE.

Query Interface

Custom API SQL HTTP / REST

Storage Architecture

Hybrid

Durability is attained through a REDO log, no UNDO logging is required since transactional state is kept in memory and persistent state is only changed at COMMIT both for in-memory and disk columns. The REDO log is logical, so only records the operations and its new values.

System Architecture

Shared-Nothing

RonDB Logo
Website

https://www.rondb.com/

Source Code

https://github.com/logicalclocks/rondb

Tech Docs

https://docs.rondb.com/

Twitter

@RonDB_ai

Developer

Hopsworks AB

Country of Origin

SE

Start Year

2020

Former Name

MySQL NDB Cluster

Project Type

Open Source

Written in

C++

Derived From

NDB Cluster

Operating Systems

Hosted, Linux, OS X

Licenses

GPL v2