DBMS > Dolt vs. MySQL vs. OrigoDB vs. VoltDB

System Properties Comparison Dolt vs. MySQL vs. OrigoDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A MySQL compatible DBMS with Git-like versioning of data and schema

Widely used open source RDBMS

A fully ACID in-memory object graph database

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

Key/Value like access via memcached API

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

github.com/dolthub/dolt
www.dolthub.com

www.mysql.com

origodb.com

www.voltdb.com

Technical documentation

Developer

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

VoltDB Inc.

Initial release

2018

1995

2009

under the name LiveDB

2010

Current release

8.4.0, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java, C++

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X

for development

Data scheme

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.

yes

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

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

.Net

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

proprietary syntax

yes

Java

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

Multi-source replication
Source-replica replication

Source-replica replication

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

not for MyISAM storage engine

depending on model

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Write ahead log

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

Only one user is configurable, and must be specified in the config file at startup

Users with fine-grained authorization concept

no user groups or roles

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.