DBMS > Drizzle vs. EsgynDB vs. etcd vs. Faircom EDGE vs. SQLite

System Properties Comparison Drizzle vs. EsgynDB vs. etcd vs. Faircom EDGE 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

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

A distributed reliable key-value store

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Key-value store

Key-value store
Relational DBMS

Relational DBMS

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

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.esgyn.cn

etcd.io
github.com/etcd-io/etcd

www.faircom.com/products/faircom-edge

www.sqlite.org

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

www.sqlite.org/docs.html

Developer

Drizzle project, originally started by Brian Aker

Esgyn

FairCom Corporation

Dwayne Richard Hipp

Initial release

2008

2015

1979

2000

Current release

7.2.4, September 2012

3.4, August 2019

V3, October 2020

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Apache Version 2.0

commercial

Restricted, free version available

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

C++

C++, Java

ANSI C, C++

Server operating systems

FreeBSD
Linux
OS X

Linux

FreeBSD
Linux
Windows

experimental

Android
Linux

ARM, x86
Raspbian
Windows

server-less

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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 SQL queries

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

gRPC
JSON over HTTP

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

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

Java Stored Procedures

yes

.Net, JavaScript, C/C++

Triggers

hooks for callbacks inside the server can be used.

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

Synchronous and asynchronous realtime replication based on transaction logs

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

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.