DBMS > Apache Doris vs. Drizzle vs. EsgynDB vs. Ignite vs. SQLite

System Properties Comparison Apache Doris vs. Drizzle vs. EsgynDB vs. Ignite vs. SQLite

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.57
Rank	#244	Overall
	#113	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

www.esgyn.cn

ignite.apache.org

www.sqlite.org

Technical documentation

github.com/apache/doris/wiki

apacheignite.readme.io/docs

www.sqlite.org/docs.html

Developer

Apache Software Foundation, originally contributed from Baidu

Drizzle project, originally started by Brian Aker

Esgyn

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2017

2008

2015

2000

Current release

1.2.2, February 2023

7.2.4, September 2012

Apache Ignite 2.6

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

GNU GPL

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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

C++, Java, .Net

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux

Linux
OS X
Solaris
Windows

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
MySQL client

JDBC

ADO.NET
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Java
PHP
Python
Ruby
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Java Stored Procedures

yes (compute grid and cache interceptors can be used instead)

Triggers

hooks for callbacks inside the server can be used.

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

yes (replicated cache)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

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

via file-system locks

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

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.