DBMS > Dolt vs. Drizzle vs. Hawkular Metrics vs. Tigris

System Properties Comparison Dolt vs. Drizzle vs. Hawkular Metrics vs. Tigris

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.

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Relational DBMS

Time Series DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Document store

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

Score	0.96
Rank	#193	Overall
	#90	Relational DBMS

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

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

www.hawkular.org

www.tigrisdata.com

Technical documentation

docs.dolthub.com

www.hawkular.org/hawkular-metrics/docs/user-guide

www.tigrisdata.com/docs

Developer

DoltHub Inc

Drizzle project, originally started by Brian Aker

Community supported by Red Hat

Tigris Data, Inc.

Initial release

2018

2008

2014

2022

Current release

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

Apache 2.0

Open Source

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

Java

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X

Linux
OS X
Windows

Linux
macOS
Windows

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

CLI Client
HTTP REST

JDBC

HTTP REST

CLI Client
gRPC
RESTful HTTP 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

C
C++
Java
PHP

Go
Java
Python
Ruby

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

yes

currently in alpha release

Triggers

yes

hooks for callbacks inside the server can be used.

yes

via Hawkular Alerting

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

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

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using FoundationDB

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

Access rights for users and roles

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

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

Radar Trends to Watch: July 2022 – O'Reilly
5 July 2022, oreilly.com

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

provided by Google News

Waiting for Red Hat OpenShift 4.0? Too late, 4.1 has already arrived… • DEVCLASS
5 June 2019, DevClass

provided by Google News

Tigris Data Unveils Beta Launch of New Vector Search Tool
19 May 2023, Datanami

Tigris Data Launches All-in-One Developer Data Platform
27 September 2022, Datanami

Latest Asigra platform targets SaaS backup for MSPs
6 March 2023, TechTarget

FerretDB Provides Alternative to MongoDB
19 May 2023, Datanami

provided by Google News

Share this page