DBMS > Apache Phoenix vs. Google Cloud Spanner vs. Percona Server for MySQL vs. Snowflake

System Properties Comparison Apache Phoenix vs. Google Cloud Spanner vs. Percona Server for MySQL vs. Snowflake

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 horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	2.89
Rank	#103	Overall
	#52	Relational DBMS

Score	2.03
Rank	#122	Overall
	#57	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

cloud.google.com/spanner

www.percona.com/software/mysql-database/percona-server

www.snowflake.com

Technical documentation

phoenix.apache.org

cloud.google.com/spanner/docs

www.percona.com/downloads/Percona-Server-LATEST

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Google

Percona

Snowflake Computing Inc.

Initial release

2014

2017

2008

2014

Current release

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

8.0.36-28, 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2

commercial

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

C and C++

Server operating systems

Linux
Unix
Windows

hosted

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

support of semi-structured data formats (JSON, XML, Avro)

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

yes

Query statements complying to ANSI 2011

yes

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

ADO.NET
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication with 3 replicas for regional instances.

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

Users with fine-grained authorization concept, user roles and pluggable authentication

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.