DBMS > Apache Drill vs. Apache Phoenix vs. Google Cloud Firestore vs. MySQL vs. Tarantool

System Properties Comparison Apache Drill vs. Apache Phoenix vs. Google Cloud Firestore vs. MySQL vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

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

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

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

Widely used open source RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

drill.apache.org

phoenix.apache.org

firebase.google.com/products/firestore

www.mysql.com

www.tarantool.io

Technical documentation

drill.apache.org/docs

phoenix.apache.org

firebase.google.com/docs/firestore

dev.mysql.com/doc

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2014

2017

1995

2008

Current release

1.20.3, January 2023

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

8.4.0, April 2024

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

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

Implementation language

Java

C and C++

Server operating systems

Linux
OS X
Windows

Linux
Unix
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

BSD
Linux
macOS

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Open binary protocol

Supported programming languages

C++

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

yes

proprietary syntax

Lua, C and SQL stored procedures

Triggers

yes, with Cloud Functions

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes, cooperative multitasking

Durability

Support for making data persistent

Depending on the underlying data source

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Depending on the underlying data source

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Users with fine-grained authorization concept

no user groups or roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.