DBMS > Apache Phoenix vs. Google Cloud Firestore vs. ScyllaDB vs. Snowflake

System Properties Comparison Apache Phoenix vs. Google Cloud Firestore vs. ScyllaDB 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

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.

Cassandra and DynamoDB compatible wide column store

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

Primary database model

Secondary database models

Key-value store

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	4.75
Rank	#68	Overall
	#5	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

firebase.google.com/products/firestore

www.scylladb.com

www.snowflake.com

Technical documentation

phoenix.apache.org

firebase.google.com/docs/firestore

docs.scylladb.com

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Google

ScyllaDB

Snowflake Computing Inc.

Initial release

2014

2017

2015

2014

Current release

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

ScyllaDB Open Source 5.4.1, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

Open Source (AGPL), commercial license available

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

Java

C++

Server operating systems

Linux
Unix
Windows

hosted

Linux

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

schema-free

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

cluster global secondary indices

SQL

Support of SQL

yes

SQL-like DML and DDL statements (CQL)

yes

APIs and other access methods

JDBC

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

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

CLI Client
JDBC
ODBC

Supported programming languages

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

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

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

yes, Lua

user defined functions

Triggers

yes, with Cloud Functions

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

selectable replication factor

Representation of geographical distribution of servers is possible

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Atomicity and isolation are supported for single operations

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

in-memory tables

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. Security Rules for 3rd party authentication using Firebase Auth.

Access rights for users can be defined per object

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

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» 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.