DBMS > Amazon DynamoDB vs. Apache Doris vs. Databend vs. Drizzle vs. EsgynDB

System Properties Comparison Amazon DynamoDB vs. Apache Doris vs. Databend vs. Drizzle vs. EsgynDB

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

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

An MPP-based analytics DBMS embracing the MySQL protocol

An open-source, elastic, and workload-aware cloud data warehouse designed to meet businesses' massive-scale analytics needs at low cost and with low complexity

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

Primary database model

Document store
Key-value store

Relational DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.57
Rank	#244	Overall
	#113	Relational DBMS

Score	0.30
Rank	#287	Overall
	#130	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Website

aws.amazon.com/dynamodb

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

github.com/datafuselabs/databend
www.databend.com

www.esgyn.cn

Technical documentation

docs.aws.amazon.com/dynamodb

github.com/apache/doris/wiki

docs.databend.com

Developer

Amazon

Apache Software Foundation, originally contributed from Baidu

Databend Labs

Drizzle project, originally started by Brian Aker

Esgyn

Initial release

2012

2017

2021

2008

2015

Current release

1.2.2, February 2023

1.0.59, April 2023

7.2.4, September 2012

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

GNU GPL

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Rust

C++

C++, Java

Server operating systems

hosted

Linux

hosted
Linux
macOS

FreeBSD
Linux
OS X

Linux

Data scheme

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

yes

APIs and other access methods

RESTful HTTP API

JDBC
MySQL client

CLI Client
JDBC
RESTful HTTP API

JDBC

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

Go
Java
JavaScript (Node.js)
Python
Rust

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

yes

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.