DBMS > Dolt vs. MySQL vs. Rockset vs. TerminusDB

System Properties Comparison Dolt vs. MySQL vs. Rockset vs. TerminusDB

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 scalable, reliable search and analytics service in the cloud, built on RocksDB

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Graph DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Relational DBMS
Search engine

Document store
RDF store

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

Score	0.93
Rank	#194	Overall
	#90	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	1.07
Rank	#180	Overall
	#31	Document stores

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

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

www.mysql.com

rockset.com

terminusdb.com

Technical documentation

docs.dolthub.com

dev.mysql.com/doc

docs.rockset.com

terminusdb.github.io/terminusdb/#

Developer

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Rockset

DataChemist Ltd.

Initial release

2018

1995

2019

2018

Current release

9.0.0, July 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C and C++

C++

Prolog, Rust

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

Read-only SQL queries, including JOINs

SQL-like query language (WOQL)

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

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

Go
Java
JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Automatic sharding

Graph Partitioning

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

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

in-memory journaling

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

Access rights for users and organizations can be defined via Rockset console

Role-based access control

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.