DBMS > Apache Phoenix vs. CouchDB vs. Databricks vs. MySQL

System Properties Comparison Apache Phoenix vs. CouchDB vs. Databricks vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Widely used open source RDBMS

Primary database model

Relational DBMS

Document store

Document store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	1.90
Rank	#125	Overall
	#59	Relational DBMS

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	84.24
Rank	#14	Overall
	#2	Document stores
	#9	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

phoenix.apache.org

docs.couchdb.org/en/stable

docs.databricks.com

dev.mysql.com/doc

Developer

Apache Software Foundation

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

Databricks

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2005

2013

1995

Current release

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

3.3.3, December 2023

9.0.0, July 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Erlang

C and C++

Server operating systems

Linux
Unix
Windows

Android
BSD
Linux
OS X
Solaris
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

Flexible Schema (defined schema, partial schema, 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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

with Databricks SQL

yes

with proprietary extensions

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native 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

Python
R
Scala

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

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

user defined functions and aggregates

yes

proprietary syntax

Triggers

yes

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

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

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

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.