DBMS > Apache Phoenix vs. CouchDB vs. MySQL vs. SWC-DB vs. Yanza

System Properties Comparison Apache Phoenix vs. CouchDB vs. MySQL vs. SWC-DB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Widely used open source RDBMS

A high performance, scalable Wide Column DBMS

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

Time Series DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

phoenix.apache.org

couchdb.apache.org

www.mysql.com

github.com/kashirin-alex/swc-db
www.swcdb.org

yanza.com

Technical documentation

phoenix.apache.org

docs.couchdb.org/en/stable

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Oracle

since 2010, originally MySQL AB, then Sun

Alex Kashirin

Yanza

Initial release

2014

2005

1995

2020

2015

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.3.3, December 2023

8.4.0, April 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL V3

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

Java

Erlang

C and C++

C++

Server operating systems

Linux
Unix
Windows

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Proprietary protocol
Thrift

HTTP API

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

C++

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Access rights for users can be defined per database

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.