DBMS > Apache Phoenix vs. EXASOL vs. Google Cloud Firestore vs. Snowflake vs. Transbase

System Properties Comparison Apache Phoenix vs. EXASOL vs. Google Cloud Firestore vs. Snowflake vs. Transbase

Editorial information provided by DB-Engines

Name

Description

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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.

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store

Relational DBMS

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

phoenix.apache.org

www.exasol.com

firebase.google.com/products/firestore

www.snowflake.com

www.transaction.de/en/products/transbase.html

Technical documentation

phoenix.apache.org

www.exasol.com/resources

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

www.transaction.de/en/products/transbase/features.html

Developer

Apache Software Foundation

Exasol

Google

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2014

2000

2017

2014

1987

Current release

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

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

free development license

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

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

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

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

SQL

Support of SQL

yes

APIs and other access methods

JDBC

.Net
JDBC
ODBC
WebSocket

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

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Java
Lua
Python
R

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

JavaScript (Node.js)
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

user defined functions

yes

Triggers

yes

yes, with Cloud Functions

similar concept for controling cloud resources

yes

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

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

yes

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 according to SQL-standard

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, user roles and pluggable authentication

fine grained access rights according to SQL-standard

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.