DBMS > Dolt vs. Drizzle vs. Postgres-XL vs. TerminusDB

System Properties Comparison Dolt vs. Drizzle vs. Postgres-XL vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Relational DBMS

Graph DBMS

Secondary database models

Document store

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

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

www.postgres-xl.org

terminusdb.com

Technical documentation

docs.dolthub.com

www.postgres-xl.org/documentation

terminusdb.github.io/terminusdb/#

Developer

DoltHub Inc

Drizzle project, originally started by Brian Aker

DataChemist Ltd.

Initial release

2018

2008

2014

since 2012, originally named StormDB

2018

Current release

7.2.4, September 2012

10 R1, October 2018

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

Mozilla public license

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X

Linux
macOS

Linux

Data scheme

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

SQL-like query language (WOQL)

APIs and other access methods

CLI Client
HTTP REST

JDBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

C
C++
Java
PHP

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

yes

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

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

Journaling Streams

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

Transaction concepts

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

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Dolt- A Version Controlled Database
29 January 2024, iProgrammer

Top Data Version Control Tools for Machine Learning Research in 2023
24 July 2023, MarkTechPost

Dolt, a Relational Database with Git-Like Cloning Features
19 August 2020, The New Stack

Data Versioning at Scale: Chaos and Chaos Management
10 February 2023, InfoQ.com

Are you still not using Version Control for Data?
11 April 2020, Towards Data Science

provided by Google News

How TerminusDB is commercializing its open source graph database
16 March 2021, VentureBeat

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

Dublin-based data collaboration tool TerminusDB raises €3.6 million in seed round
15 March 2021, Tech.eu

[MCR2030-CAMS-ARISE-UNDRR Webinar] Preventing cascading failures of critical assets: Using the Open-Source ...
12 April 2022, United Nations Office for Disaster Risk Reduction

Trinity College spinout TerminusDB secures €3.6m in investment
15 March 2021, The Irish Times

provided by Google News

Share this page