DBMS > Apache Drill vs. etcd vs. MySQL vs. TigerGraph vs. Yanza

System Properties Comparison Apache Drill vs. etcd vs. MySQL vs. TigerGraph vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed reliable key-value store

Widely used open source RDBMS

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Time Series DBMS for IoT Applications

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

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

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

drill.apache.org

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

www.mysql.com

www.tigergraph.com

yanza.com

Technical documentation

drill.apache.org/docs

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

dev.mysql.com/doc

docs.tigergraph.com

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Yanza

Initial release

2012

1995

2017

2015

Current release

1.20.3, January 2023

3.4, August 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

with proprietary extensions

SQL-like query language (GSQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

HTTP API

Supported programming languages

C++

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

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

C++
Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

yes

Triggers

yes, watching key changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Relationships in graphs

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Users with fine-grained authorization concept

no user groups or roles

Role-based access control

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.