DBMS > Dolt vs. MySQL vs. Sqrrl vs. Trafodion

System Properties Comparison Dolt vs. MySQL vs. Sqrrl vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Widely used open source RDBMS

Adaptable, secure NoSQL built on Apache Accumulo

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store

Document store
Spatial DBMS

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

Website

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

www.mysql.com

sqrrl.com

trafodion.apache.org

Technical documentation

docs.dolthub.com

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

DoltHub Inc

Oracle

since 2010, originally MySQL AB, then Sun

Amazon

originally Sqrrl Data, Inc.

Apache Software Foundation, originally developed by HP

Initial release

2018

1995

2012

2014

Current release

9.0.0, July 2024

2.3.0, February 2019

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

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

Java

C++, Java

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

CLI Client
HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

making use of Hadoop

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

selectable replication factor

making use of Hadoop

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Immediate 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

Atomic updates per row, document, or graph entity

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.