DBMS > Apache Doris vs. Drizzle vs. EsgynDB vs. Riak KV

System Properties Comparison Apache Doris vs. Drizzle vs. EsgynDB vs. Riak KV

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

An MPP-based analytics DBMS embracing the MySQL protocol

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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

Score	0.69
Rank	#237	Overall
	#108	Relational DBMS

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Website

doris.apache.org
github.com/apache/doris

www.esgyn.cn

Technical documentation

github.com/apache/doris/wiki

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation, originally contributed from Baidu

Drizzle project, originally started by Brian Aker

Esgyn

OpenSource, formerly Basho Technologies

Initial release

2017

2008

2015

2009

Current release

1.2.2, February 2023

7.2.4, September 2012

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

commercial

Open Source

Apache version 2, commercial enterprise edition

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

Java

C++

C++, Java

Erlang

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux

Linux
OS X

Data scheme

yes

schema-free

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

restricted

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
MySQL client

JDBC

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

Java

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Erlang

Triggers

hooks for callbacks inside the server can be used.

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

yes, using Riak Security

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

Migrating from ClickHouse to Apache Doris: Boosting OLAP Performance
9 October 2023, hackernoon.com

How Big Data Is Saving Lives in Real Time: IoV Data Analytics Helps Prevent Accidents
28 November 2023, KDnuggets

LLM-Powered OLAP: the Tencent Experience with Apache Doris
28 August 2023, hackernoon.com

Apache Doris just 'graduated': Why care about this SQL data warehouse
24 June 2022, InfoWorld

How to Digest 15 Billion Logs Per Day and Keep Big Queries Within 1 Second
1 September 2023, KDnuggets

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho distributes Riak to more customers - DCD
28 November 2013, DatacenterDynamics

provided by Google News

Share this page