DBMS > Apache Doris vs. Drizzle vs. OrigoDB vs. Vitess

System Properties Comparison Apache Doris vs. Drizzle vs. OrigoDB vs. Vitess

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.

A fully ACID in-memory object graph database

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.61
Rank	#235	Overall
	#110	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

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

origodb.com

vitess.io

Technical documentation

github.com/apache/doris/wiki

origodb.com/docs

vitess.io/docs

Developer

Apache Software Foundation, originally contributed from Baidu

Drizzle project, originally started by Brian Aker

Robert Friberg et al

The Linux Foundation, PlanetScale

Initial release

2017

2008

2009

under the name LiveDB

2013

Current release

1.2.2, February 2023

7.2.4, September 2012

15.0.2, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux
Windows

Docker
Linux
macOS

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

with proprietary extensions

APIs and other access methods

JDBC
MySQL client

JDBC

.NET Client API
HTTP API
LINQ

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java

C
C++
Java
PHP

.Net

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Triggers

hooks for callbacks inside the server can be used.

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica 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

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

depending on model

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role based authorization

Users with fine-grained authorization concept

no user groups or 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

Migrating from ClickHouse to Apache Doris: Boosting OLAP Performance
9 October 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

Apache Doris Analytical Database Graduates from Apache Incubator
20 June 2022, Datanami

StarRocks’ real-time analytics engine moves to the cloud
14 July 2022, SiliconANGLE News

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page