DBMS > Apache Drill vs. Google Cloud Firestore vs. Microsoft Azure Table Storage vs. Snowflake vs. TerarkDB

System Properties Comparison Apache Drill vs. Google Cloud Firestore vs. Microsoft Azure Table Storage vs. Snowflake vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

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

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.

A Wide Column Store for rapid development using massive semi-structured datasets

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store
Relational DBMS

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	7.85
Rank	#51	Overall
	#8	Document stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

drill.apache.org

firebase.google.com/products/firestore

azure.microsoft.com/en-us/services/storage/tables

www.snowflake.com

github.com/bytedance/terarkdb

Technical documentation

drill.apache.org/docs

firebase.google.com/docs/firestore

docs.snowflake.net/manuals/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Google

Microsoft

Snowflake Computing Inc.

ByteDance, originally Terark

Initial release

2012

2017

2012

2014

2016

Current release

1.20.3, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

restricted open source version 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

C++

Server operating systems

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

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

schema-free

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

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP API

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

C++

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

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

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

Implicit feature of the cloud service

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

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

User concepts

Access control

Depending on the underlying data source

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 based on private key authentication or shared access signatures

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.