DBMS > Dolt vs. Drizzle vs. Geode vs. ToroDB

System Properties Comparison Dolt vs. Drizzle vs. Geode vs. ToroDB

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.

ToroDB seems to be discontinued. Therefore it 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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Relational DBMS

Key-value store

Document store

Secondary database models

Document store

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

Score	1.02
Rank	#191	Overall
	#89	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Website

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

geode.apache.org

github.com/torodb/server

Technical documentation

docs.dolthub.com

geode.apache.org/docs

Developer

DoltHub Inc

Drizzle project, originally started by Brian Aker

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

8Kdata

Initial release

2018

2008

2002

2016

Current release

7.2.4, September 2012

1.1, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

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

Java

Server operating systems

Linux
macOS
Windows

FreeBSD
Linux
OS X

All OS with a Java VM

the JDK (8 or later) is also required

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

SQL-like query language (OQL)

APIs and other access methods

CLI Client
HTTP REST

JDBC

Java Client API
Memcached protocol
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

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

yes

currently in alpha release

user defined functions

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

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

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

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

Concurrency

Support for concurrent manipulation of data

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights per client and object definable

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

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

25 Hot New Data Tools and What They DON'T Do
14 May 2020, Towards Data Science

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, O'Reilly Media

provided by Google News

Share this page